AI agents call get_innings_progression 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 a cricket statistics database to retrieve and display innings progression metrics. It has no side effects, cannot modify data, execute code, delete records, or move money. The data returned is purely informational analysis of historical cricket performance.
From the tool's definition Tool retrieves historical match data: 'Over-by-over progression showing runs per over, cumulative runs, wickets, and run rate for a single match innings.' This is a query operation that returns analytical data about past cricket matches with no modification…
Attacks that exploit this kind of access
How did the scoring unfold over by over? Over-by-over progression showing runs per over, cumulative runs, wickets, and run rate for a single match innings. 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_innings_progression: 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_innings_progression 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_innings_progression 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_innings_progression. 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_innings_progression 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 →