delete_account
Soft-delete a CRM account/customer. This releases the primary phone for future reuse while keeping account history for audit.
This record as markdown: /tools/io-favcrm-favcrm/delete-account.md
What delete_account does on FavCRM
AI agents call delete_account to permanently remove resources in FavCRM, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
accountId | string | Yes | The account ID to soft-delete |
Parameters from the server's own tool schema.
Why delete_account is rated Critical
Although audit history is retained, the account deletion is irreversible from an operational standpoint—the customer record is removed from active service and the phone number is freed for reassignment. This prevents any undo of the deletion action itself. This is a destructive operation with high blast radius in a CRM context, as it could accidentally remove important customer relationships and business data.
From the tool's definition Tool name is 'delete_account' and description states it performs a 'Soft-delete' of a 'CRM account/customer'.
Attacks that exploit this kind of access
The rule that runs delete_account safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_account, this is the rule to start with:
delete_account is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every delete_account call is checked against it from then on.
Questions about delete_account
Soft-delete a CRM account/customer. This releases the primary phone for future reuse while keeping account history for audit. It is categorised as a Destructive tool in the FavCRM MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_account accepts 1 parameter: accountId. Required: accountId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM 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 FavCRM. Nothing to install.
delete_account 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_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.
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.
delete_account is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
Across the catalogue