fetch_llms_txt
AI agents call fetch_llms_txt to retrieve information from FetchV2 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves content (likely fetching an llms.txt file from a web source based on naming convention). No description was provided, but the naming pattern and sibling tools indicate data retrieval with no side effects. Confidence is slightly reduced due to empty description, but context strongly suggests a read operation.
From the tool's definition Tool name 'fetch_llms_txt' and sibling tools 'discover_links', 'fetch', 'fetch_batch' all retrieve web content without modifying data. Server description states it 'enables fetching webpages' and 'extracting clean content' — read-only operations.
Attacks that exploit this kind of access
fetch_llms_txt. It is categorised as a Read tool in the FetchV2 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FetchV2 MCP Server MCP server in PolicyLayer and add a rule for fetch_llms_txt: 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 FetchV2 MCP Server. Nothing to install.
fetch_llms_txt 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_llms_txt 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_llms_txt. 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_llms_txt is provided by the FetchV2 MCP Server MCP server (praveenc/fetchv2-mcp-server). 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 →