Eliminar, remover o quitar una tarea / task con nombre 'name' de la lista llamada 'listname'
AI agents call delete_a_task to permanently remove resources in Interview — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes tasks from lists without the ability to undo the action. Deletion is irreversible and represents data loss, placing it in the Destructive category rather than Write (which is reversible modification). An AI agent misusing this tool could delete all tasks from a user's todo lists, causing significant data loss.
From the tool's definition Tool name 'delete_a_task' combined with description 'Eliminar, remover o quitar una tarea' (Spanish: 'Delete, remove, or remove a task') indicates irreversible deletion of task data.
Attacks that exploit this kind of access
Eliminar, remover o quitar una tarea / task con nombre 'name' de la lista llamada 'listname'. It is categorised as a Destructive tool in the Interview MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Interview MCP server in PolicyLayer and add a rule for delete_a_task: 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 Interview. Nothing to install.
delete_a_task 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_a_task 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_a_task. 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_a_task is provided by the Interview MCP server (matilarrazabal/mcp-server-interview). 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 →