Remove a task by its ID
AI agents call remove_task to permanently remove resources in Productivity Tracker MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'remove_task' tool permanently deletes task data, which cannot be undone. Deletion is irreversible and represents data loss. This is more severe than Write (which is reversible) or Execute (which may have side effects but are not inherently destructive). An AI agent misusing this could permanently erase user productivity records, causing data loss with no recovery path.
From the tool's definition Tool name 'remove_task' and description 'Remove a task by its ID' indicate irreversible deletion of task records from the SQLite database.
Attacks that exploit this kind of access
Remove a task by its ID. It is categorised as a Destructive tool in the Productivity Tracker MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Productivity Tracker MCP Server MCP server in PolicyLayer and add a rule for remove_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 Productivity Tracker MCP Server. Nothing to install.
remove_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 remove_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 remove_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.
remove_task is provided by the Productivity Tracker MCP Server MCP server (manasamadgul/tracker). 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 →