Download the text from a URL.
AI agents call fetch_url_text to retrieve information from Web Search Neo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and extracts content from web pages without side effects. No data is created, modified, deleted, or executed. The operation is passive and idempotent. Even if an agent fetches malicious content, the tool itself performs only data retrieval. Risk is low because exposure is limited to what the agent does with downloaded text, not the tool's inherent capability.
From the tool's definition Tool description explicitly states 'Download the text from a URL' — a retrieval operation with no modification, deletion, or execution capability. Server description confirms it 'enables fetching and extracting text from URLs', reinforcing read-only semantics.
Attacks that exploit this kind of access
Download the text from a URL. It is categorised as a Read tool in the Web Search Neo MCP Server, which means it retrieves data without modifying state.
Register the Web Search Neo MCP server in PolicyLayer and add a rule for fetch_url_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 Web Search Neo. Nothing to install.
fetch_url_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_url_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_url_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_url_text is provided by the Web Search Neo MCP server (neoxider/web-search-neo). 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 →