AI agents call bbs_debug_llm_stats to retrieve information from Mcp Bbs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports usage metrics and statistics. It performs no modifications, deletions, or external operations. The data returned is observational in nature and cannot alter system state. This is a straightforward Read category tool with low severity since misuse would only expose informational data about LLM usage patterns, not cause operational harm.
From the tool's definition Tool name and description indicate retrieval of statistics ('Get LLM usage statistics including tokens, cost, and cache hit rates'). The verb 'Get' is a query operation with no side effects.
Attacks that exploit this kind of access
Get LLM usage statistics including tokens, cost, and cache hit rates. It is categorised as a Read tool in the Mcp Bbs MCP Server, which means it retrieves data without modifying state.
Register the Mcp Bbs MCP server in PolicyLayer and add a rule for bbs_debug_llm_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 Mcp Bbs. Nothing to install.
bbs_debug_llm_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the bbs_debug_llm_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.
Set action: deny in the PolicyLayer policy for bbs_debug_llm_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.
bbs_debug_llm_stats is provided by the Mcp Bbs MCP server (livingstaccato/mcp-bbs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →