Browse available Fumadocs documentation sections and topics. Use without parameters to see all sections, or specify a section to see all topics in that section.
AI agents call list_topics 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 retrieves and lists documentation metadata without side effects. It is a straightforward read operation that queries available sections and topics in the Fumadocs documentation index. No data is created, modified, deleted, or executed.
From the tool's definition Tool name is 'list_topics' and description states it 'Browse available Fumadocs documentation sections and topics' with no mention of modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access list_topics 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 list_topics:
{
"version": "1",
"default": "deny",
"tools": {
"list_topics": {}
}
}list_topics 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.
Browse available Fumadocs documentation sections and topics. Use without parameters to see all sections, or specify a section to see all topics in that section. 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 list_topics: 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.
list_topics 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 list_topics 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 list_topics. 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.
list_topics 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.