cms_delete_entry
Delete an entry. Cascades to its versions and references.
This record as markdown: /tools/com-getmunin-munin/cms-delete-entry.md
What cms_delete_entry does on Munin
AI agents call cms_delete_entry 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_entry is rated Critical
This tool irreversibly deletes data (CMS entries) along with cascading deletions of related versions and references. This is a classic destructive operation that cannot be undone. The cascade behavior increases the blast radius, as a single delete call can remove multiple interconnected records.
From the tool's definition The tool name is 'cms_delete_entry' and the description explicitly states 'Delete an entry. Cascades to its versions and references.' The verb 'delete' combined with 'cascades' indicates irreversible removal of data and dependent records.
Attacks that exploit this kind of access
The rule that runs cms_delete_entry 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_entry, this is the rule to start with:
cms_delete_entry 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_entry call is checked against it from then on.
Questions about cms_delete_entry
Delete an entry. Cascades to its 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_entry: 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_entry 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_entry 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_entry. 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_entry 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