Critical Risk →

usage_stats

View or reset tool usage statistics. Put your REQUEST in the

Part of the Tachibot server.

usage_stats can permanently delete data in Tachibot, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE TACHIBOT →

Free to start. No card required.

AI agents may call usage_stats to permanently remove or destroy resources in Tachibot. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer 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 Tachibot. There is no undo for destructive operations. PolicyLayer 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "usage_stats"
  ]
}

See the full Tachibot policy for all 104 tools.

Get this rule live on your own Tachibot server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TACHIBOT →

View all 104 tools →

These attack patterns abuse exactly the kind of access usage_stats gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so usage_stats only ever does what you allow.

SECURE TACHIBOT →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the usage_stats tool do? +

View or reset tool usage statistics. Put your REQUEST in the. It is categorised as a Destructive tool in the Tachibot 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? +

Register the Tachibot MCP server in PolicyLayer and add a rule for usage_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 Tachibot. Nothing to install.

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

Set action: deny in the PolicyLayer 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 Tachibot MCP server (tachibot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Tachibot tool call.

Deterministic rules across all 104 Tachibot tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.