AI agents call get_player_comparison 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 retrieves and compares existing cricket statistics between two players. It performs a query operation against the DuckDB database without creating, modifying, deleting, or executing any operations. The comparison is a read-only analytical function with no side effects or blast radius if misused by an AI agent—the worst outcome would be returning irrelevant statistical comparisons.
From the tool's definition Tool name 'get_player_comparison' and description 'Side-by-side batting or bowling stats for two players under the same filters' indicates retrieval of cricket statistics data with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
How do two players compare? Side-by-side batting or bowling stats for two players under the same filters. 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_player_comparison: 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_player_comparison 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_player_comparison 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_player_comparison. 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_player_comparison 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 →