AI agents call get_emerging_players 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 historical cricket statistics and derives insights through comparison operations. It has no side effects, does not create or modify records, does not execute arbitrary code or commands, and does not delete or alter data. The scope is limited to analytical read operations on a static DuckDB database of historical cricket deliveries.
From the tool's definition Tool performs statistical analysis and comparison of cricket player performance metrics (average, strike rate, economy, wickets per match) without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Which players are improving the most? Compares recent season stats to career baseline to find players whose average, strike rate, economy, or wickets per match have significantly improved. 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_emerging_players: 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_emerging_players 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_emerging_players 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_emerging_players. 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_emerging_players 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 →