Delete a contact's phone number.
AI agents call delete_contact_phone to permanently remove resources in CATS MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes a phone number record from a contact in the CATS applicant tracking system. This is an irreversible data deletion operation. While the blast radius is contained to a single contact field rather than an entire record, deletion operations fall under the Destructive category by definition.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a contact's phone number' — irreversibly removes contact data.
Attacks that exploit this kind of access
Delete a contact's phone number. It is categorised as a Destructive tool in the CATS MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CATS MCP Server MCP server in PolicyLayer and add a rule for delete_contact_phone: 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 CATS MCP Server. Nothing to install.
delete_contact_phone 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_phone 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_phone. 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_phone is provided by the CATS MCP Server MCP server (vanman2024/cats-mcp-server). 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 →