AI agents call get_player_form 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 performs a read-only query against the DuckDB database to retrieve cricket statistics and performance metrics. It has no side effects, creates no new data, executes no external operations, and makes no financial transactions. The blast radius of misuse is minimal—an agent could only retrieve data it's authorized to access. This is a straightforward Read category tool with low severity.
From the tool's definition Tool name is 'get_player_form' and description states it 'Returns the last N innings with individual scores, strike rates, opposition, venue, and dismissal info' — purely retrieves and queries historical performance data from the cricket database with no…
Attacks that exploit this kind of access
How has this player been performing recently? Returns the last N innings with individual scores, strike rates, opposition, venue, and dismissal info. 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_form: 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_form 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_form 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_form. 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_form 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 →