Low Risk

fetch_url

Fetch content from a URL.

How to control fetch_url ↓

What fetch_url does on McpVanguard

AI agents call fetch_url to retrieve information from McpVanguard without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why fetch_url needs a policy

This tool retrieves data from a remote URL without modifying, deleting, or executing code. It is a Read operation. Severity is medium rather than low because fetching arbitrary URLs could enable data exfiltration, SSRF attacks (if internal URLs are accessible), or retrieval of sensitive information, especially in an AI agent context where URL targets may be attacker-controlled or inadvertently point to sensitive…

From the tool's definition Tool description states 'Fetch content from a URL,' which is a retrieval operation with no persistent side effects.

Documented attack patterns abuse exactly the kind of access fetch_url gives an agent:

How to control fetch_url

PolicyLayer is an MCP gateway — it sits between your AI agents and McpVanguard, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_url:

policy.json
{
  "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.

  1. Create a free account and register McpVanguard — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about fetch_url

What does the fetch_url tool do? +

Fetch content from a URL. It is categorised as a Read tool in the McpVanguard MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch_url? +

Register the McpVanguard 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 McpVanguard. Nothing to install.

What risk level is fetch_url? +

fetch_url is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fetch_url? +

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.

How do I block fetch_url completely? +

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.

What MCP server provides fetch_url? +

fetch_url is provided by the McpVanguard MCP server (provnai/mcpvanguard). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every McpVanguard tool call.

Start from McpVanguard, 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.

4 McpVanguard tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.