Fetch a single documentation URL.
AI agents call fetch-doc-source to retrieve information from Uefn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves documentation from a URL with no side effects. It is a straightforward read operation that queries and returns data. The low severity reflects that fetching documentation poses minimal risk even if invoked by an AI agent, as it cannot modify state, execute code, or cause destructive changes. The high confidence reflects the clear, explicit description of the tool's purpose.
From the tool's definition Tool name 'fetch-doc-source' and description 'Fetch a single documentation URL' indicate retrieval of documentation content without modification or execution.
Documented attack patterns abuse exactly the kind of access fetch-doc-source gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Uefn, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch-doc-source:
{
"version": "1",
"default": "deny",
"tools": {
"fetch-doc-source": {}
}
}fetch-doc-source 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.
Fetch a single documentation URL. It is categorised as a Read tool in the Uefn MCP Server, which means it retrieves data without modifying state.
Register the Uefn MCP server in PolicyLayer and add a rule for fetch-doc-source: 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 Uefn. Nothing to install.
fetch-doc-source 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-doc-source 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-doc-source. 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-doc-source is provided by the Uefn MCP server (quangdang46/uefn-verse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Uefn, 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.
143 Uefn tools catalogued and risk-classified — across an index of 43,000+ MCP servers.