Search for cricket players by name. Returns player IDs, names, and country. Use this to look up a cricketer before fetching more detail.
AI agents call search_players 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). |
search | string | Yes | Player name to search for, e.g. "Kohli", "Root". |
_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 cricket player data and returns read-only information (IDs, names, countries). It performs a lookup operation without creating, modifying, deleting, or executing any actions. The sibling tool 'bet_research' suggests the server may support financial operations, but this specific tool is purely informational retrieval.
From the tool's definition Tool description states 'Search for cricket players by name. Returns player IDs, names, and country.' The verb 'search' and 'returns' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Search for cricket players by name. Returns player IDs, names, and country. Use this to look up a cricketer before fetching more detail. It is categorised as a Read tool in the Mcp Cricket MCP Server, which means it retrieves data without modifying state.
search_players accepts 3 parameters: offset, search, _apiKey. Required: search. 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 search_players: 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.
search_players 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_players 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_players. 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_players 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 →