AI agents call delete_contact to permanently remove resources in PhonePi MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a contact is an irreversible action that permanently removes data from the user's phone. This qualifies as Destructive rather than Write (which is reversible). The severity is high because an AI agent with access to this tool could delete important contacts without user oversight, disrupting communication and business relationships. The confidence is high because the intent and effect are unambiguous.
From the tool's definition Tool name is 'delete_contact' and description states 'Delete a contact from the phone' — uses the verb 'Delete' which indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_contact gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PhonePi MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_contact:
{
"version": "1",
"default": "deny",
"hide": [
"delete_contact"
]
}delete_contact disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a contact from the phone. It is categorised as a Destructive tool in the PhonePi MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PhonePi 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 PhonePi 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 PhonePi MCP server (priyankark/phonepi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 22 PhonePi MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
22 PhonePi MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.