AI agents call get_situational_stats to retrieve information from Cricket without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval tool that queries a cricket statistics database and returns filtered historical records. It has no side effects—it does not create, modify, delete data, or trigger external operations. The tool operates within a read-only analytics context on historical sports data. Misuse by an AI agent would at worst return irrelevant cricket statistics, with no meaningful blast radius.
From the tool's definition Tool name 'get_situational_stats' and description indicate querying/filtering of historical batting statistics by match situation (chasing, setting, pressure, position). No modification, deletion, execution, or financial operations are described.
Attacks that exploit this kind of access
How does a player bat when chasing / setting / under pressure / at a specific position? Batting stats filtered by match situation. It is categorised as a Read tool in the Cricket MCP Server, which means it retrieves data without modifying state.
Register the Cricket MCP server in PolicyLayer and add a rule for get_situational_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 Cricket. Nothing to install.
get_situational_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_situational_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_situational_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_situational_stats is provided by the Cricket MCP server (mavaali/cricket-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 →