Delete a phone record
AI agents call delete_phone to permanently remove resources in CiviCRM MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes phone contact information from a CiviCRM contact record. While not as critical as deleting entire contacts or financial records, deletion of phone numbers is irreversible and could impair communication with individuals. The blast radius is bounded to a single phone record per invocation, justifying 'high' rather than 'critical' severity.
From the tool's definition Tool name is 'delete_phone' with description 'Delete a phone record'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a phone record. It is categorised as a Destructive tool in the CiviCRM MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CiviCRM MCP Server MCP server in PolicyLayer and add a rule for delete_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 CiviCRM MCP Server. Nothing to install.
delete_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_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_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_phone is provided by the CiviCRM MCP Server MCP server (johncallhub/civicrm-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 →