Search Fumadocs documentation by keyword. Returns matching documentation pages with titles, descriptions, and paths. Use this to find specific topics or features.
AI agents call search_docs to retrieve information from Fumadocs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries documentation and returns results. It performs information retrieval only, matching the 'Read' category definition (search, list, get, fetch). The blast radius of misuse is minimal—an agent cannot cause harm by searching documentation. Severity is low because there are no destructive, financial, or code-execution consequences.
From the tool's definition Tool name 'search_docs' and description states it 'Search[es] Fumadocs documentation by keyword. Returns matching documentation pages' — a pure retrieval operation with no side effects, no data modification, and no external operations triggered.
Documented attack patterns abuse exactly the kind of access search_docs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fumadocs, and nothing reaches the server without passing your rules. This is the rule we recommend for search_docs:
{
"version": "1",
"default": "deny",
"tools": {
"search_docs": {}
}
}search_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.
Search Fumadocs documentation by keyword. Returns matching documentation pages with titles, descriptions, and paths. Use this to find specific topics or features. It is categorised as a Read tool in the Fumadocs MCP Server, which means it retrieves data without modifying state.
Register the Fumadocs MCP server in PolicyLayer and add a rule for search_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 Fumadocs. Nothing to install.
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 search_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 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.
search_docs is provided by the Fumadocs MCP server (k4cper-g/fumadocs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Fumadocs, 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.
5 Fumadocs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.