Critical Risk →

usage_stats

Check your current daily usage quota. Shows verifications used today, remaining allowance, pricing tier, and reset time.

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

AI agents may call usage_stats to permanently remove or destroy resources in Prospector. 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 usage_stats in a loop, permanently destroying resources in Prospector. 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.

myceliumlabs-prospector-mcp-email-finder.yaml
tools:
  usage_stats:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Prospector policy for all 5 tools.

Tool Name usage_stats
Category Destructive
Risk Level Critical

Agents calling destructive-class tools like usage_stats 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.

usage_stats is one of the critical-risk operations in Prospector. 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 usage_stats tool do? +

Check your current daily usage quota. Shows verifications used today, remaining allowance, pricing tier, and reset time.. It is categorised as a Destructive tool in the Prospector 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 usage_stats? +

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

What risk level is usage_stats? +

usage_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 usage_stats? +

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

Set action: deny in the Intercept policy for usage_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 usage_stats? +

usage_stats is provided by the Prospector MCP server (MyceliumLabs/prospector-mcp-email-finder). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Prospector

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.