New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

cms_delete_entry

Delete an entry. Cascades to its versions and references.

SERVERMunin SOURCEhttps://mcp.getmunin.com/mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade D, identity unverified Pull the record →

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.

Questions about cms_delete_entry

What does the cms_delete_entry tool do? +

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.

How do I enforce a policy on cms_delete_entry? +

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.

What risk level is cms_delete_entry? +

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.

Can I rate-limit cms_delete_entry? +

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.

How do I block cms_delete_entry completely? +

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.

What MCP server provides cms_delete_entry? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Munin's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.