ID
AI agents call delete-task to permanently remove resources in MCP Person Registration System — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion operations cannot be undone and result in permanent data loss. Even though the blast radius is limited to individual tasks (not system-wide destruction), the irreversible nature of deletion and potential for accidental removal of important records justifies 'high' severity. Confidence is high due to the clear destructive intent in the tool name, despite the minimal description provided.
From the tool's definition Tool named 'delete-task' with description 'ID' indicates deletion of task records. The name explicitly uses 'delete' which is a destructive operation that irreversibly removes data from the database.
Attacks that exploit this kind of access
ID. It is categorised as a Destructive tool in the MCP Person Registration System MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Person Registration System MCP server in PolicyLayer and add a rule for delete-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 MCP Person Registration System. Nothing to install.
delete-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-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-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-task is provided by the MCP Person Registration System MCP server (zeyneptncr/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 →