get_player_statistics
AI agents call get_player_statistics to retrieve information from Soccer MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read operation that retrieves player statistics from a sports data API. It has no capability to modify, delete, execute code, or create financial obligations. The blast radius of misuse is minimal—worst case, an agent repeatedly queries the API causing rate limiting or data exposure of publicly available sports information.
From the tool's definition Tool name 'get_player_statistics' follows the 'get_' prefix pattern consistent with all sibling tools (get_all_leagues_id, get_fixture_events, get_league_info, etc.), all of which are read-only data retrieval operations.
Attacks that exploit this kind of access
get_player_statistics. It is categorised as a Read tool in the Soccer MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Soccer MCP Server MCP server in PolicyLayer and add a rule for get_player_statistics: 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 Soccer MCP Server. Nothing to install.
get_player_statistics 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 get_player_statistics 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 get_player_statistics. 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.
get_player_statistics is provided by the Soccer MCP Server MCP server (obinopaul/soccer-mcp-server). 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 →