Critical Risk →

delete_contact

Delete a contact

How to control delete_contact ↓

What delete_contact does on Frontapp MCP Server

AI agents call delete_contact 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.

Critical Risk

Why delete_contact needs a policy

Deleting a contact is an irreversible operation that cannot be undone—it permanently removes customer/contact data from the system. This qualifies as Destructive rather than Write (which is reversible). The severity is high because losing contact records impacts business operations, customer relationships, and data integrity, though it may not directly affect financial systems (which would be critical).

From the tool's definition Tool name is 'delete_contact' with description 'Delete a contact'. The verb 'delete' indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access delete_contact gives an agent:

How to control delete_contact

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:

policy.json
{
  "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.

  1. Create a free account and register Frontapp MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_contact

What does the delete_contact tool do? +

Delete 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.

How do I enforce a policy on delete_contact? +

Register the Frontapp MCP Server 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 Frontapp MCP Server. Nothing to install.

What risk level is delete_contact? +

delete_contact is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_contact? +

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.

How do I block delete_contact completely? +

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.

What MCP server provides delete_contact? +

delete_contact 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.

Enforce policy on every Frontapp MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.