AI agents call statistics to retrieve information from Basic without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only statistical calculations (e.g., mean, median, standard deviation) on input data. It does not modify, store, or transmit any data, and has no side effects. Misuse potential is minimal as it only processes numbers provided to it.
From the tool's definition "Calculate statistical measures for a set of numbers" — pure computation with no side effects
Attacks that exploit this kind of access
Calculate statistical measures for a set of numbers. It is categorised as a Read tool in the Basic MCP Server, which means it retrieves data without modifying state.
Register the Basic MCP server in PolicyLayer and add a rule for statistics: 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 Basic. Nothing to install.
statistics 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 statistics 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 statistics. 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.
statistics is provided by the Basic MCP server (msilverblatt/basic-mcp). 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 →