AI agents call search_matches 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 search/query operation that retrieves historical cricket match data from the DuckDB database. It has no capability to modify, delete, execute code, or trigger external actions. The blast radius of misuse is negligible — an agent cannot harm data or systems through search alone.
From the tool's definition Tool description states it 'Find[s] specific matches' and 'Returns match results' — purely retrieves and queries data with no modification or side effects. The parameters (date, teams, format, venue, tournament) are all read-only filters.
Attacks that exploit this kind of access
Find specific matches. Search by date, teams, format, venue, or tournament. Returns match results with teams, scores, venue, date, outcome, and player of the match. 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 search_matches: 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.
search_matches 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 search_matches 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 search_matches. 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.
search_matches 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 →