Critical Risk →

delete_attachment

Delete an attachment

How to control delete_attachment ↓

What delete_attachment does on TheBrain MCP Server

AI agents call delete_attachment to permanently remove resources in TheBrain MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_attachment needs a policy

Destructive category applies because the tool permanently removes data without recovery mechanism. While the blast radius is limited to individual attachments rather than entire datasets, deletion is irreversible. Severity is high rather than critical because impact is scoped to single attachments; critical would apply if this could cascade-delete or wipe entire knowledge bases.

From the tool's definition delete_attachment performs irreversible deletion of file attachments. The verb 'delete' indicates data removal that cannot be undone.

Documented attack patterns abuse exactly the kind of access delete_attachment gives an agent:

How to control delete_attachment

PolicyLayer is an MCP gateway — it sits between your AI agents and TheBrain MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_attachment:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_attachment"
  ]
}

delete_attachment disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register TheBrain MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_attachment

What does the delete_attachment tool do? +

Delete an attachment. It is categorised as a Destructive tool in the TheBrain MCP Server 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 delete_attachment? +

Register the TheBrain MCP Server MCP server in PolicyLayer and add a rule for 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 TheBrain MCP Server. Nothing to install.

What risk level is delete_attachment? +

delete_attachment 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 delete_attachment? +

Yes. Add a rate_limit block to the 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.

How do I block delete_attachment completely? +

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

What MCP server provides delete_attachment? +

delete_attachment is provided by the TheBrain MCP Server MCP server (redmorestudio/thebrain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every TheBrain MCP Server tool call.

Start from TheBrain MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

26 TheBrain MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.