Overview
web_fetch lets the agent make outbound HTTP requests. It supports all common HTTP methods, custom headers, request bodies, and can optionally extract readable text from HTML pages.
Every request passes through SsrfGuard before execution - a defense layer that blocks private IP ranges, cloud metadata endpoints, and DNS rebinding attacks.
Tool: web_fetch
Security level: moderate | Tier: Essential
Full URL to fetch. Must be a valid
http:// or https:// URL.HTTP method:
GET, POST, PUT, DELETE.Custom request headers as key-value pairs.
Request body for
POST or PUT. Typically JSON-encoded.Request timeout in seconds. Maximum enforced by server policy.
Extract readable text content from HTML pages (strips tags, navigation, scripts).
Examples
Response
A successful fetch returns:Content Limits
Responses are capped at 500KB. Larger responses are truncated. For large downloads, consider fetching a specific resource path rather than a whole page.SSRF Protection
TheSsrfGuard blocks requests to:
| Category | Examples |
|---|---|
| Loopback | 127.0.0.1, ::1, localhost |
| Private networks | 10.x.x.x, 172.16-31.x.x, 192.168.x.x |
| Link-local | 169.254.x.x (includes cloud metadata at 169.254.169.254) |
| Cloud metadata | metadata.google.internal, metadata.internal |
| Reserved ranges | RFC 1918 + all IANA special-use ranges |