Use this to fetch documentation from a given URL.
AI agents call fetch_docs to retrieve information from MCP LLMS-TXT Documentation Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and reads documentation content from a specified URL. It has no capability to modify, delete, or execute operations; it is purely a data retrieval function. The severity is low because fetching documentation poses minimal risk — the worst case is retrieval of sensitive or unexpected documentation content, which can be mitigated through URL validation and access controls.
From the tool's definition Tool description states 'fetch documentation from a given URL' — this is a retrieval operation with no modification or execution of external code.
Documented attack patterns abuse exactly the kind of access fetch_docs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP LLMS-TXT Documentation Server, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_docs:
{
"version": "1",
"default": "deny",
"tools": {
"fetch_docs": {}
}
}fetch_docs 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.
Use this to fetch documentation from a given URL. It is categorised as a Read tool in the MCP LLMS-TXT Documentation Server MCP Server, which means it retrieves data without modifying state.
Register the MCP LLMS-TXT Documentation Server MCP server in PolicyLayer and add a rule for fetch_docs: 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 LLMS-TXT Documentation Server. Nothing to install.
fetch_docs 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_docs 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_docs. 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_docs is provided by the MCP LLMS-TXT Documentation Server MCP server (teddylee777/mcpdoc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP LLMS-TXT Documentation Server, 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 MCP LLMS-TXT Documentation Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.