Fetch content from any URL and convert to plain text format
AI agents call fetch-text to retrieve information from MCP URL Fetcher without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reads web content, converting it to plain text. It has no side effects on the source data or system—it only queries and returns information. This is a straightforward Read operation with low severity since it poses minimal security risk when used by an AI agent (potential concerns are limited to accessing sensitive or private URLs, but the tool itself is not destructive or harmful).
From the tool's definition Tool name 'fetch-text' and description 'Fetch content from any URL and convert to plain text format' indicate retrieval of data with no modification, deletion, or code execution capabilities.
Attacks that exploit this kind of access
Fetch content from any URL and convert to plain text format. It is categorised as a Read tool in the MCP URL Fetcher MCP Server, which means it retrieves data without modifying state.
Register the MCP URL Fetcher MCP server in PolicyLayer and add a rule for fetch-text: 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 MCP URL Fetcher. Nothing to install.
fetch-text 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-text 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-text. 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-text is provided by the MCP URL Fetcher MCP server (nathanonn/mcp-url-fetcher). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →