This record as markdown: /tools/com-getmunin-munin/kb-export.md
What kb_export does on Munin
AI agents call kb_export to retrieve information from Munin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why kb_export is rated Low
The tool name 'kb_export' and partial description 'Export this org\' indicate this tool reads and exports knowledge base data. Export operations are typically read-only, retrieving data into a portable format without modifying the source. Severity is medium because it could expose the entire organization's knowledge base content. Confidence is reduced due to the truncated description leaving some ambiguity.
From the tool's definition 'Export this org\' - description appears truncated, but 'export' strongly implies reading/retrieving data from the knowledge base
Attacks that exploit this kind of access
The rule that runs kb_export safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Munin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kb_export, this is the rule to start with:
kb_export is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every kb_export call is checked against it from then on.
Questions about kb_export
Export this org\. It is categorised as a Read tool in the Munin MCP Server, which means it retrieves data without modifying state.
Register the Munin MCP server in PolicyLayer and add a rule for kb_export: 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 Munin. Nothing to install.
kb_export 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 kb_export 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 kb_export. 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.
kb_export is provided by the Munin MCP server (https://mcp.getmunin.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Munin, and thousands of servers like it.
This server
Across the catalogue