kb_delete_document
Delete a knowledge-base document. Pass
This record as markdown: /tools/com-getmunin-munin/kb-delete-document.md
What kb_delete_document does on Munin
AI agents call kb_delete_document to permanently remove resources in Munin, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why kb_delete_document is rated Critical
Deletion of documents cannot be undone and permanently removes information from the knowledge base. This is a destructive operation that warrants the highest severity category. While blast radius depends on the document's importance and scope, unauthorized deletion could cause significant harm to the organization's knowledge management system.
From the tool's definition Tool name 'kb_delete_document' with description 'Delete a knowledge-base document'—the verb 'Delete' combined with operation on persistent data (knowledge-base document) indicates irreversible data destruction.
Attacks that exploit this kind of access
The rule that runs kb_delete_document 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_delete_document, this is the rule to start with:
kb_delete_document is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every kb_delete_document call is checked against it from then on.
Questions about kb_delete_document
Delete a knowledge-base document. Pass. It is categorised as a Destructive tool in the Munin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Munin MCP server in PolicyLayer and add a rule for kb_delete_document: 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_delete_document is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the kb_delete_document 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_delete_document. 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_delete_document 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.
Across the catalogue