AI agents call get_season_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 tool queries and retrieves aggregated performance statistics from the cricket database. It performs a read-only operation that returns informational data about player seasons without creating, modifying, deleting, executing code, or committing financial transactions. The blast radius of misuse is minimal—an agent could only retrieve unwanted data, not cause operational harm.
From the tool's definition Tool name 'get_season_stats' and description 'Season-by-season career breakdown showing batting or bowling stats' indicates retrieval of historical statistical data with no modification or side effects.
Attacks that exploit this kind of access
How has this player performed year by year? Season-by-season career breakdown showing batting or bowling stats for each season. 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_season_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_season_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_season_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_season_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_season_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 →