reset-stats

Reset execution statistics for fresh testing

SERVERFrontmcp SOURCEagentfront/frontmcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/frontmcp/reset-stats.md

WHAT IT DOES

What reset-stats does on Frontmcp

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

RISK

Why reset-stats is rated Critical

Resetting statistics permanently discards accumulated execution data, which cannot be recovered. This is an irreversible destructive action on stored state, even though the blast radius is limited to statistics/metrics rather than core application data.

From the tool's definition 'Reset execution statistics' — the word 'reset' implies irreversible deletion/overwriting of accumulated statistics data

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs reset-stats 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 reset-stats, this is the rule to start with:

reset-stats Hidden

reset-stats is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "reset-stats"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every reset-stats call is checked against it from then on.

FAQ

Questions about reset-stats

What does the reset-stats tool do? +

Reset execution statistics for fresh 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.

How do I enforce a policy on reset-stats? +

Register the Front MCP server in PolicyLayer and add a rule for reset-stats: 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.

What risk level is reset-stats? +

reset-stats 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 reset-stats? +

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

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

reset-stats 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.

KEEP EXPLORING

More on Front, and thousands of servers like it.

This server

All 206 Front tools → Critical-risk tools on this server →

Across the catalogue

team_manager_reset on Team Manager MCP →reset_mcp_runtime_metrics on 0xpdf → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →