Get detailed information about a specific player by name.
AI agents call get_player_details to retrieve information from FPL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a straightforward query operation to retrieve player information from the Fantasy Premier League API. It reads existing data without creating, modifying, deleting, or executing code. The operation is informational only and poses minimal security risk, as it merely surfaces data that would be available to any FPL user querying the same player.
From the tool's definition Tool name 'get_player_details' and description 'Get detailed information about a specific player by name' indicate retrieval of player data with no modification or side effects.
Attacks that exploit this kind of access
Get detailed information about a specific player by name. It is categorised as a Read tool in the FPL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FPL MCP Server MCP server in PolicyLayer and add a rule for get_player_details: 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 FPL MCP Server. Nothing to install.
get_player_details 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_details 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_details. 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_details is provided by the FPL MCP Server MCP server (lewis-king/fpl-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 →