cms_delete_asset

Delete an asset and remove the underlying file from storage. Fails with a conflict if the asset is still referenced by any entry, as a typed asset field or inline in a body.

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-asset.md

WHAT IT DOES

What cms_delete_asset does on Munin

AI agents call cms_delete_asset 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.

RISK

Why cms_delete_asset is rated Critical

This tool permanently deletes assets and their underlying files from storage, which cannot be undone. This is a classic destructive operation that irreversibly removes data.

From the tool's definition Delete an asset and remove the underlying file from storage. The tool explicitly performs deletion ('Delete an asset') and removal ('remove the underlying file from storage'), which are irreversible operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cms_delete_asset 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_asset, this is the rule to start with:

cms_delete_asset Hidden

cms_delete_asset is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cms_delete_asset"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every cms_delete_asset call is checked against it from then on.

FAQ

Questions about cms_delete_asset

What does the cms_delete_asset tool do? +

Delete an asset and remove the underlying file from storage. Fails with a conflict if the asset is still referenced by any entry, as a typed asset field or inline in a body. 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_asset? +

Register the Munin MCP server in PolicyLayer and add a rule for cms_delete_asset: 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_asset? +

cms_delete_asset 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_asset? +

Yes. Add a rate_limit block to the cms_delete_asset 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_asset completely? +

Set action: deny in the PolicyLayer policy for cms_delete_asset. 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_asset? +

cms_delete_asset 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.

KEEP EXPLORING

More on Munin, and thousands of servers like it.

This server

All 242 Munin tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →