Retrieve web page content from a specified URL
AI agents call fetch_url to retrieve information from Fetch MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a retrieval operation only—fetching and extracting data from web pages. It has no capability to modify, delete, or execute code. The blast radius of misuse is minimal; an attacker could only read publicly or privately accessible web content that the server can reach, which is a standard Read operation.
From the tool's definition Tool description states it 'Retrieve[s] web page content from a specified URL' with no modification or execution capability mentioned. Server description confirms it extracts and converts content to Markdown format without side effects.
Documented attack patterns abuse exactly the kind of access fetch_url gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fetch MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_url:
{
"version": "1",
"default": "deny",
"tools": {
"fetch_url": {}
}
}fetch_url is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve web page content from a specified URL. It is categorised as a Read tool in the Fetch MCP MCP Server, which means it retrieves data without modifying state.
Register the Fetch MCP server in PolicyLayer and add a rule for fetch_url: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Fetch MCP. Nothing to install.
fetch_url is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the fetch_url rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for fetch_url. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
fetch_url is provided by the Fetch MCP server (jae-jae/fetcher-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Fetch MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Fetch MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.