Deletes a named file from the managed attachments folder for a Trellis issue. Errors if the issue does not exist or the named file does not exist.
AI agents call remove_attachment to permanently remove resources in Task Trellis MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes files from issue attachments without the ability to undo the action. While the blast radius is somewhat limited to attachments associated with a specific issue (reducing severity from critical to high), the irreversible nature of deletion categorizes it as Destructive rather than Write.
From the tool's definition Tool description explicitly states it 'Deletes a named file' from attachments, which is an irreversible operation. The term 'Deletes' combined with file removal from issue attachments indicates data destruction.
Documented attack patterns abuse exactly the kind of access remove_attachment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Task Trellis MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_attachment:
{
"version": "1",
"default": "deny",
"hide": [
"remove_attachment"
]
} remove_attachment disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Deletes a named file from the managed attachments folder for a Trellis issue. Errors if the issue does not exist or the named file does not exist. It is categorised as a Destructive tool in the Task Trellis MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Task Trellis MCP server in PolicyLayer and add a rule for remove_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 Task Trellis MCP. Nothing to install.
remove_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 remove_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 remove_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.
remove_attachment is provided by the Task Trellis MCP server (langadventurellc/task-trellis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Task Trellis MCP, 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.
16 Task Trellis MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.