Get full information and scorecard for a single cricket match (Test/ODI/T20) by its match ID. Returns teams, venue, innings scores, toss, and winner. Get the id from current_matches.
AI agents call match_info 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 |
|---|---|---|---|
id | string | Yes | Match ID, as returned by current_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.
match_info queries and retrieves cricket match data through CricAPI. It performs no writes, deletions, code execution, or financial transactions. The tool is purely informational and has no capability to modify data or trigger external operations with side effects. Misuse by an AI agent would be limited to excessive queries or information disclosure, representing minimal security risk.
From the tool's definition Tool description states it 'Get[s] full information and scorecard for a single cricket match' and 'Returns teams, venue, innings scores, toss, and winner.' These are all read operations that retrieve data without modification or side effects.
Attacks that exploit this kind of access
Get full information and scorecard for a single cricket match (Test/ODI/T20) by its match ID. Returns teams, venue, innings scores, toss, and winner. Get the id from current_matches. It is categorised as a Read tool in the Mcp Cricket MCP Server, which means it retrieves data without modifying state.
match_info accepts 2 parameters: id, _apiKey. Required: id. 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 match_info: 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.
match_info 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 match_info 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 match_info. 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.
match_info 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 →