Returns stats of the LODA project. This includes the number of sequences, programs, and formulas in the database.
AI agents call get_stats to retrieve information from LODA API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves aggregate statistics from the OEIS/LODA database without any side effects, data modification, code execution, or resource consumption beyond a simple query. This is a pure read operation with minimal blast radius—misuse would only retrieve non-sensitive aggregated counts.
From the tool's definition Tool returns stats and counts ('number of sequences, programs, and formulas') from the LODA database with no modification capability.
Attacks that exploit this kind of access
Returns stats of the LODA project. This includes the number of sequences, programs, and formulas in the database. It is categorised as a Read tool in the LODA API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LODA API MCP Server 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 LODA API MCP Server. Nothing to install.
get_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 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.
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.
get_stats is provided by the LODA API MCP Server MCP server (loda-lang/loda-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 →