Permanently delete a saved filter.
AI agents call delete_filter 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 irreversibly deletes data (a saved filter) without the ability to recover it. While the blast radius is limited to a filter configuration rather than critical task or project data, the permanent nature of deletion and lack of undo capability places it in the Destructive category.
From the tool's definition Tool name is 'delete_filter' and description states 'Permanently delete a saved filter.' The use of 'Permanently delete' indicates an irreversible action that cannot be undone.
Attacks that exploit this kind of access
Permanently delete a saved filter. 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_filter: 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_filter 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_filter 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_filter. 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_filter is provided by the Vikunja MCP Server MCP server (lindenlion/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 →