entitycricket_get_player
Get detailed info for a specific cricket player.
This record as markdown: /tools/io-github-lacausecrypto-sports-hub/entitycricket-get-player.md
What entitycricket_get_player does on Sports Hub
AI agents call entitycricket_get_player 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 entitycricket_get_player is rated Low
This tool queries and retrieves player information from a cricket API. It performs a GET-style operation to fetch read-only data about an athlete. There is no modification of data, no code execution, no deletion, and no financial transaction involved. The blast radius of misuse is minimal—an agent could only retrieve publicly available cricket player statistics and biographical information.
From the tool's definition Tool name 'entitycricket_get_player' and description 'Get detailed info for a specific cricket player' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs entitycricket_get_player 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 entitycricket_get_player, this is the rule to start with:
entitycricket_get_player 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 entitycricket_get_player call is checked against it from then on.
Questions about entitycricket_get_player
Get detailed info for a specific cricket player. 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 entitycricket_get_player: 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.
entitycricket_get_player 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 entitycricket_get_player 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 entitycricket_get_player. 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.
entitycricket_get_player 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