AI agents call get_match_scorecard 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 a local DuckDB database to retrieve and display static cricket statistics (runs, balls, dismissals, bowling figures, etc.). It is a read-only operation that retrieves data without side effects, modification, or triggering external actions. The low severity reflects minimal risk if misused by an AI agent, as it only returns informational cricket statistics.
From the tool's definition Tool name 'get_match_scorecard' and description stating it 'Show[s] me the full scorecard of a match' with retrieval of 'batting and bowling cards' — purely retrieves historical cricket match data with no modification, deletion, or execution of external…
Attacks that exploit this kind of access
Show me the full scorecard of a match. Complete batting and bowling cards with runs, balls, fours, sixes, strike rate, dismissals, bowling figures, extras, and totals per 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_match_scorecard: 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_match_scorecard 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_match_scorecard 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_match_scorecard. 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_match_scorecard 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 →