AI agents call delete_attachment to permanently remove resources in Taiga MCP Bridge — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion is inherently destructive and cannot be undone. This tool removes attachments from Taiga project management records. Even without a detailed description, the 'delete' verb combined with this operational context places it in the Destructive category (more severe than Write).
From the tool's definition Tool name 'delete_attachment' indicates permanent removal of data. The description is empty, preventing verification of scope, but the naming pattern aligns with other write/modify tools on this Taiga bridge (create_epic, assign_task_to_user, add_comment)…
Documented attack patterns abuse exactly the kind of access delete_attachment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Taiga MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_attachment:
{
"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.
Free to start. No card required.
delete_attachment. It is categorised as a Destructive tool in the Taiga MCP Bridge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Taiga MCP Bridge 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 Taiga MCP Bridge. Nothing to install.
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 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 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.
delete_attachment is provided by the Taiga MCP Bridge MCP server (talhaorak/pytaiga-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 94 Taiga MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
94 Taiga MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.