List current and recent cricket matches (Test/ODI/T20) with live scores, teams, venue, and status. Use this for "what cricket matches are live/on right now". Returns match IDs usable with match_info.
AI agents call current_matches to retrieve information from Mcp Cricket without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
offset | number | — | Pagination offset (default 0). Each page returns up to 25 matches. |
_apiKey | string | — | Optional — your own CricAPI key for higher limits; omit to use the shared Pipeworx key. |
Parameters from the server's own tool schema.
This tool retrieves cricket match data without side effects. It is a straightforward data-fetching operation that does not create, modify, delete, or execute operations. The severity is low because misuse would only result in excessive queries or information disclosure, not system or user harm.
From the tool's definition Tool lists current and recent cricket matches with live scores, teams, venue, and status. No modification, deletion, or code execution occurs. The description uses query verbs like 'list' and explicitly serves to retrieve data for informational purposes.
Attacks that exploit this kind of access
List current and recent cricket matches (Test/ODI/T20) with live scores, teams, venue, and status. Use this for "what cricket matches are live/on right now". Returns match IDs usable with match_info. It is categorised as a Read tool in the Mcp Cricket MCP Server, which means it retrieves data without modifying state.
current_matches accepts 2 parameters: offset, _apiKey. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Cricket MCP server in PolicyLayer and add a rule for current_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 Mcp Cricket. Nothing to install.
current_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 current_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 current_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.
current_matches is provided by the Mcp Cricket MCP server (https://gateway.pipeworx.io/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 →