cricket_get_player_info

Get detailed profile and statistics for a specific cricket player

SERVERSports Hub SOURCEmcp-sports-hub

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/io-github-lacausecrypto-sports-hub/cricket-get-player-info.md

WHAT IT DOES

What cricket_get_player_info does on Sports Hub

AI agents call cricket_get_player_info 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.

RISK

Why cricket_get_player_info is rated Low

This tool retrieves and queries cricket player information. It has no side effects, does not modify data, execute code, delete records, or involve financial transactions. It is a straightforward read operation consistent with similar sports API tools (apifootball_get_players, apifootball_get_fixtures, etc.) on the same server.

From the tool's definition Tool name contains 'get_' and description states 'Get detailed profile and statistics' — pure data retrieval with no modification, deletion, or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cricket_get_player_info 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_player_info, this is the rule to start with:

cricket_get_player_info Allowed

cricket_get_player_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cricket_get_player_info": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sports Hub, apply this rule, and every cricket_get_player_info call is checked against it from then on.

FAQ

Questions about cricket_get_player_info

What does the cricket_get_player_info tool do? +

Get detailed profile and statistics 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.

How do I enforce a policy on cricket_get_player_info? +

Register the Sports Hub MCP server in PolicyLayer and add a rule for cricket_get_player_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 Sports Hub. Nothing to install.

What risk level is cricket_get_player_info? +

cricket_get_player_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cricket_get_player_info? +

Yes. Add a rate_limit block to the cricket_get_player_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.

How do I block cricket_get_player_info completely? +

Set action: deny in the PolicyLayer policy for cricket_get_player_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.

What MCP server provides cricket_get_player_info? +

cricket_get_player_info 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.

KEEP EXPLORING

More on Sports Hub, and thousands of servers like it.

This server

All 396 Sports Hub tools →

Across the catalogue

get_team_info on CTFtime MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →