Retrieve full documentation content from a URL and return it as rendered markdown. Use this tool to get complete pages — including code examples, API signatures, and prose — from search_docs result URLs. - Pass a URL directly from search_docs results to retrieve that section's full content. - Tr...
Accepts URL/endpoint input (url); Admin/system-level operation
Part of the Docfork MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call fetch_doc to retrieve information from Docfork without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though fetch_doc only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
fetch_doc:
rules:
- action: allowSee the full Docfork policy for all 2 tools.
Agents calling read-class tools like fetch_doc have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Retrieve full documentation content from a URL and return it as rendered markdown. Use this tool to get complete pages — including code examples, API signatures, and prose — from search_docs result URLs. - Pass a URL directly from search_docs results to retrieve that section's full content. - Trim the URL anchor or path to a parent directory to get a broader table of contents with section previews. - Returns rendered markdown that preserves code blocks, headings, and document structure. - Only works on Docfork-indexed documentation — use WebFetch for URLs not returned by search_docs. - If search_docs returns sparse or no results, try fetch_doc on the library's root documentation URL (e.g. https://github.com/owner/repo/tree/main/docs) to browse available content.. It is categorised as a Read tool in the Docfork MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for fetch_doc. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Docfork MCP server.
fetch_doc 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 rule in your Intercept 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 Intercept policy for fetch_doc. 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 is provided by the Docfork MCP server (docfork). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept