AI agents call get_venue_stats 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 is a pure data retrieval tool that answers analytical questions about venue-level cricket statistics. It reads from a database without side effects, making it a Read category risk. Severity is low because the worst outcome of misuse would be exposure of historical sports statistics—already public knowledge—with no operational, destructive, or financial impact.
From the tool's definition Tool retrieves historical cricket statistics (matches played, average scores, totals, win percentages) from a local DuckDB database. The description explicitly queries data: 'scoring patterns', 'average scores', 'highest/lowest totals', 'win %'.
Attacks that exploit this kind of access
What are the scoring patterns at this ground? Venue statistics: matches played, average first/second innings scores, highest and lowest totals, and bat-first win %. 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_venue_stats: 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_venue_stats 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_venue_stats 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_venue_stats. 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_venue_stats 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 →