Critical Risk →

apps_reset

Delete all analytics data for an app (sessions, events, users, crashes, etc.) while keeping the app record and keys intact, via /i/apps/reset. Requires global admin privileges. WARNING: irreversible. To also remove the app itself use apps_delete.

Admin/system-level operation

Part of the Countly MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

countly-mcp-server Destructive

AI agents may call apps_reset to permanently remove or destroy resources in Countly. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call apps_reset in a loop, permanently destroying resources in Countly. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

countly.yaml
tools:
  apps_reset:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Countly policy for all 127 tools.

Tool Name apps_reset
Category Destructive
MCP Server Countly MCP Server
Risk Level Critical

View all 127 tools →

Agents calling destructive-class tools like apps_reset have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

apps_reset is one of the critical-risk operations in Countly. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the apps_reset tool do? +

Delete all analytics data for an app (sessions, events, users, crashes, etc.) while keeping the app record and keys intact, via /i/apps/reset. Requires global admin privileges. WARNING: irreversible. To also remove the app itself use apps_delete.. It is categorised as a Destructive tool in the Countly 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 apps_reset? +

Add a rule in your Intercept YAML policy under the tools section for apps_reset. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Countly MCP server.

What risk level is apps_reset? +

apps_reset 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 apps_reset? +

Yes. Add a rate_limit block to the apps_reset rule in your Intercept 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 apps_reset completely? +

Set action: deny in the Intercept policy for apps_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.

What MCP server provides apps_reset? +

apps_reset is provided by the Countly MCP server (countly-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.