conv_delete_attachment
Permanently delete an image attached to a conversation message. The stored file is erased. An attachment on a message that has already been sent or received keeps its filename, type and size on the thread so the record still shows something was attached, and stops being viewable; an attachment no...
This record as markdown: /tools/com-getmunin-munin/conv-delete-attachment.md
What conv_delete_attachment does on Munin
AI agents call conv_delete_attachment 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 conv_delete_attachment is rated Critical
Irreversibly erases files; cannot be undone once deleted from storage.
From the tool's definition Permanently delete an image attached to a conversation message. The stored file is erased.
Attacks that exploit this kind of access
The rule that runs conv_delete_attachment 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 conv_delete_attachment, this is the rule to start with:
conv_delete_attachment 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 conv_delete_attachment call is checked against it from then on.
Questions about conv_delete_attachment
Permanently delete an image attached to a conversation message. The stored file is erased. An attachment on a message that has already been sent or received keeps its filename, type and size on the thread so the record still shows something was attached, and stops being viewable; an attachment not yet on a message is removed outright. Already-deleted attachments report alreadyDeleted rather than failing. 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 conv_delete_attachment: 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.
conv_delete_attachment 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 conv_delete_attachment 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 conv_delete_attachment. 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.
conv_delete_attachment 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