Search documentation across GitHub repositories or the web. For targeted searches INSIDE a specific library's documentation, use the docforkIdentifier parameter (author/repo format). Extract from GitHub URLs (e.g., github.com/facebook/react → 'facebook/react') and include in ALL subsequent search...
Accepts freeform code/query input (query); Single-target operation
Part of the Docfork MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call docfork_search_docs 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 docfork_search_docs 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:
docfork_search_docs:
rules:
- action: allowSee the full Docfork policy for all 2 tools.
Agents calling read-class tools like docfork_search_docs 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.
Search documentation across GitHub repositories or the web. For targeted searches INSIDE a specific library's documentation, use the docforkIdentifier parameter (author/repo format). Extract from GitHub URLs (e.g., github.com/facebook/react → 'facebook/react') and include in ALL subsequent searches about that library for focused, accurate results.. 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 docfork_search_docs. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Docfork MCP server.
docfork_search_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 docfork_search_docs 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 docfork_search_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.
docfork_search_docs is provided by the Docfork MCP server (docfork/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