get_stats

Return the live stats snapshot (get_stats RPC).

SERVERBusymate DevTools SOURCEhttps://mcp.busymate.dev

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-busymate-busymate-devtools/get-stats.md

WHAT IT DOES

What get_stats does on Busymate DevTools

AI agents call get_stats to retrieve information from Busymate DevTools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_stats is rated Low

This tool retrieves live statistics data in a read-only manner. It has no capacity to modify, execute, delete, or move money. The blast radius of misuse is minimal—an AI agent could access debugging/traffic statistics but cannot cause harm beyond information disclosure. Statistics snapshots are typically non-sensitive operational metrics.

From the tool's definition Tool name 'get_stats' and description 'Return the live stats snapshot' indicate a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_stats safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Busymate DevTools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_stats, this is the rule to start with:

get_stats Allowed

get_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_stats": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Busymate DevTools, apply this rule, and every get_stats call is checked against it from then on.

FAQ

Questions about get_stats

What does the get_stats tool do? +

Return the live stats snapshot (get_stats RPC). It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_stats? +

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

What risk level is get_stats? +

get_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_stats? +

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

Set action: deny in the PolicyLayer policy for get_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 get_stats? +

get_stats is provided by the Busymate DevTools MCP server (https://mcp.busymate.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Busymate DevTools, and thousands of servers like it.

This server

All 44 Busymate DevTools tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →