delete_candidate_phone
AI agents call delete_candidate_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 verb 'delete' maps directly to the Destructive category as defined. Removing a candidate's phone number is an irreversible operation that cannot be undone through normal tool use. While the impact is narrower than deleting an entire candidate record, deletion of specific personal contact data still constitutes a destructive action.
From the tool's definition Tool name 'delete_candidate_phone' explicitly contains 'delete', which removes data irreversibly. Description is empty, preventing full confirmation, but the name alone strongly indicates deletion of phone contact information for a candidate record.
Attacks that exploit this kind of access
delete_candidate_phone. 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_candidate_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_candidate_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_candidate_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_candidate_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_candidate_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 →