Get documentation for a specific Fumadocs UI component. Includes props, usage examples, and configuration options. Available components: accordion, tabs, codeblock, steps, files, banner, and more.
AI agents call get_component 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 and returns Fumadocs component documentation without modifying state, executing code, or triggering side effects. It is purely informational retrieval, consistent with sibling tools like 'get_page' and 'search_docs' on the same server. No financial, destructive, or execution risks present.
From the tool's definition Tool retrieves documentation for UI components, returning static informational content (props, usage examples, configuration options). The verb 'Get' and the passive nature of documentation lookup indicate no data modification, deletion, or external execution.
Documented attack patterns abuse exactly the kind of access get_component 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 get_component:
{
"version": "1",
"default": "deny",
"tools": {
"get_component": {}
}
}get_component 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.
Get documentation for a specific Fumadocs UI component. Includes props, usage examples, and configuration options. Available components: accordion, tabs, codeblock, steps, files, banner, and more. 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 get_component: 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.
get_component 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 get_component 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 get_component. 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.
get_component 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.