AI agents call get_batting_records 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 tool queries and retrieves historical cricket statistics from a database. It performs read-only operations to fetch aggregated player batting records such as runs, averages, centuries, etc. There are no side effects, no data modification, no code execution, and no destructive operations. The low severity reflects the minimal risk profile—misuse would only retrieve sports statistics data that is already public.
From the tool's definition Tool retrieves batting leaderboards and statistics ('Who has the most runs / highest average / most centuries'). The description explicitly indicates query and ranking operations with no mention of modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
Who has the most runs / highest average / most centuries? Batting leaderboards ranking players by runs, average, strike rate, centuries, fifties, sixes, fours, or highest score. 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_batting_records: 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_batting_records 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_batting_records 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_batting_records. 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_batting_records 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 →