Get a lightweight feed of live cricket scores across current matches. Returns each match as a compact "team1 vs team2" with running scores and status. Best for quick live cricket score checks.
AI agents call match_scores 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 |
|---|---|---|---|
_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 queries and returns live cricket match data without creating, modifying, deleting, or executing any operations. It has no side effects beyond retrieving information. The scope is limited to reading publicly available cricket scores, making it low-risk even if misused by an AI agent.
From the tool's definition Tool description states 'Get a lightweight feed of live cricket scores' and is designed for 'quick live cricket score checks.' The verb 'Get' and the read-only nature of retrieving score data with no modification capability indicate a pure data retrieval…
Attacks that exploit this kind of access
Get a lightweight feed of live cricket scores across current matches. Returns each match as a compact "team1 vs team2" with running scores and status. Best for quick live cricket score checks. It is categorised as a Read tool in the Mcp Cricket MCP Server, which means it retrieves data without modifying state.
match_scores accepts 1 parameter: _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 match_scores: 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_scores 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_scores 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_scores. 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_scores 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 →