Critical Risk →

delete_account

Delete an account

How to control delete_account ↓

What delete_account does on Frontapp MCP Server

AI agents call delete_account 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_account needs a policy

This tool permanently removes an account, which is an irreversible operation that cannot be undone. Deletion operations are classified as Destructive. The severity is high because deleting an account would destroy all associated customer communication records, contacts, and conversation history in a production customer communication platform, representing significant data loss.

From the tool's definition Tool name 'delete_account' combined with description 'Delete an account' explicitly performs irreversible deletion of an account and all associated data.

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

How to control delete_account

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_account:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_account"
  ]
}

delete_account 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_account

What does the delete_account tool do? +

Delete an account. 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_account? +

Register the Frontapp MCP Server MCP server in PolicyLayer and add a rule for delete_account: 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_account? +

delete_account 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_account? +

Yes. Add a rate_limit block to the delete_account 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_account completely? +

Set action: deny in the PolicyLayer policy for delete_account. 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_account? +

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