crm-reset
Reset CRM store to initial seed data (for testing)
This record as markdown: /tools/frontmcp/crm-reset.md
What crm-reset does on Frontmcp
AI agents call crm-reset 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 crm-reset is rated Critical
This tool destroys all current CRM data without recovery option by reverting to initial state. While labeled 'for testing', a malicious or mistaken invocation would cause permanent data loss. This is irreversible destruction of data, not merely a modification. The high severity reflects the broad blast radius of losing an entire CRM dataset.
From the tool's definition Tool resets CRM store to initial seed data, which irreversibly overwrites existing data in the store. The explicit mention of 'reset' paired with a CRM data store indicates data loss.
Attacks that exploit this kind of access
The rule that runs crm-reset 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 crm-reset, this is the rule to start with:
crm-reset 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 crm-reset call is checked against it from then on.
Questions about crm-reset
Reset CRM store to initial seed data (for testing). 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 crm-reset: 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.
crm-reset 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 crm-reset 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 crm-reset. 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.
crm-reset 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