Delete a contact or all contacts
AI agents call delete_contact to permanently remove resources in AutoBot MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes personal data (contacts) with no undo capability. While not as critical as financial or system-level destruction, the loss of user contacts represents significant data loss. Severity is high due to the potential for bulk deletion ('all contacts') and the sensitive nature of contact information. An AI agent misusing this could permanently erase a user's contact list.
From the tool's definition Tool name 'delete_contact' with description 'Delete a contact or all contacts' explicitly performs irreversible deletion of contact data. The 'all contacts' variant demonstrates potential for bulk destruction.
Attacks that exploit this kind of access
Delete a contact or all contacts. It is categorised as a Destructive tool in the AutoBot MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AutoBot MCP server in PolicyLayer and add a rule for delete_contact: 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 AutoBot MCP. Nothing to install.
delete_contact 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_contact 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_contact. 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_contact is provided by the AutoBot MCP server (yz0903/autobot-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 →