cms_delete_collection
Delete a collection. Cascades to all entries, versions, and references.
This record as markdown: /tools/com-getmunin-munin/cms-delete-collection.md
What cms_delete_collection does on Munin
AI agents call cms_delete_collection 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 cms_delete_collection is rated Critical
This tool performs an irreversible deletion operation that cascades across all entries, versions, and references within a collection. This is a destructive action with no undo capability. The blast radius is high because cascading deletes can remove large amounts of dependent data. While not financial, this is more severe than Execute or Write operations because the effects cannot be reversed.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a collection. Cascades to all entries, versions, and references.' — irreversible removal affecting multiple dependent entities.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs cms_delete_collection 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 cms_delete_collection, this is the rule to start with:
cms_delete_collection 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 cms_delete_collection call is checked against it from then on.
Questions about cms_delete_collection
Delete a collection. Cascades to all entries, versions, and references. 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 cms_delete_collection: 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.
cms_delete_collection 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 cms_delete_collection 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 cms_delete_collection. 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.
cms_delete_collection 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