Delete an attachment from a task
AI agents call delete_task_attachment to permanently remove resources in Vikunja MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a file attachment from a task, which cannot be undone. Deletion of data is irreversible and falls under the Destructive category. While the blast radius is limited to a single attachment rather than entire projects or tasks, the permanent loss of the attachment justifies 'high' severity.
From the tool's definition Tool name and description: 'delete_task_attachment' - 'Delete an attachment from a task'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete an attachment from a task. It is categorised as a Destructive tool in the Vikunja MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vikunja MCP Server MCP server in PolicyLayer and add a rule for delete_task_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 Vikunja MCP Server. Nothing to install.
delete_task_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_task_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_task_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_task_attachment is provided by the Vikunja MCP Server MCP server (wosh-i/vikunja-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →