AI agents call delete_contact_handle to permanently remove resources in Frontapp 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 a contact handle (communication channel identifier such as email or phone number) from a contact record. This action cannot be undone and represents data destruction. While not as severe as deleting an entire contact, removing a handle prevents future communication through that channel and may disrupt business operations if the handle is critical.
From the tool's definition The tool is named 'delete_contact_handle' and described as 'Delete a handle from a contact'. The verb 'delete' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_contact_handle gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Frontapp MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_contact_handle:
{
"version": "1",
"default": "deny",
"hide": [
"delete_contact_handle"
]
}delete_contact_handle 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 handle from a contact. It is categorised as a Destructive tool in the Frontapp MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Frontapp MCP Server MCP server in PolicyLayer and add a rule for delete_contact_handle: 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 Frontapp MCP Server. Nothing to install.
delete_contact_handle 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_handle 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_handle. 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_handle is provided by the Frontapp MCP Server MCP server (zqushair/frontapp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Frontapp MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
151 Frontapp MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.