This record as markdown: /tools/io-github-lacausecrypto-sports-hub/cricket-get-players.md
What cricket_get_players does on Sports Hub
AI agents call cricket_get_players to retrieve information from Sports Hub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why cricket_get_players is rated Low
This is a straightforward read operation that searches and retrieves cricket player information. It has no capability to modify data, execute code, delete records, or perform any financial transactions. The blast radius of misuse is minimal—an agent could retrieve player data but cannot cause harm through this tool alone.
From the tool's definition Tool name 'cricket_get_players' and description 'Search for cricket players by name' indicate a query/search operation that retrieves player data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs cricket_get_players safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sports Hub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cricket_get_players, this is the rule to start with:
cricket_get_players is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sports Hub, apply this rule, and every cricket_get_players call is checked against it from then on.
Questions about cricket_get_players
Search for cricket players by name. It is categorised as a Read tool in the Sports Hub MCP Server, which means it retrieves data without modifying state.
Register the Sports Hub MCP server in PolicyLayer and add a rule for cricket_get_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 Sports Hub. Nothing to install.
cricket_get_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 cricket_get_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 cricket_get_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.
cricket_get_players is provided by the Sports Hub MCP server (mcp-sports-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sports Hub, and thousands of servers like it.
This server
Across the catalogue