This record as markdown: /tools/frontmcp/users-delete.md
What users-delete does on Frontmcp
AI agents call users-delete to permanently remove resources in Frontmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why users-delete is rated Critical
This tool permanently removes user records from a CRM system. Deletion is an irreversible operation with significant blast radius—lost customer data, broken relationships, audit trail gaps, and potential compliance violations. While not financial in nature, it qualifies as Destructive (higher severity than Write) due to its irreversible nature.
From the tool's definition Tool name 'users-delete' and description 'Delete a user from the CRM' explicitly indicate irreversible deletion of user data.
Attacks that exploit this kind of access
The rule that runs users-delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For users-delete, this is the rule to start with:
users-delete 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 Frontmcp, apply this rule, and every users-delete call is checked against it from then on.
Questions about users-delete
Delete a user from the CRM. It is categorised as a Destructive tool in the Frontmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Front MCP server in PolicyLayer and add a rule for users-delete: 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 Frontmcp. Nothing to install.
users-delete 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 users-delete 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 users-delete. 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.
users-delete is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
Across the catalogue