Delete a task in Motion
AI agents call deleteTask to permanently remove resources in Example Next Js MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool deletes a task, which is an irreversible operation that cannot be undone. Even though the blast radius is scoped to a single task (not a database wipe), deletion is categorically Destructive. Severity is high because an AI agent with unconstrained access could delete many user tasks if misdirected or compromised, causing data loss and workflow disruption.
From the tool's definition Tool name is 'deleteTask' and description states 'Delete a task in Motion' — the verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a task in Motion. It is categorised as a Destructive tool in the Example Next Js MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Example Next Js MCP Server MCP server in PolicyLayer and add a rule for deleteTask: 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 Example Next Js MCP Server. Nothing to install.
deleteTask 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 deleteTask 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 deleteTask. 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.
deleteTask is provided by the Example Next Js MCP Server MCP server (mat-hiretalk/mcp-assistant). 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 →