Compare multiple players side-by-side using their names.
AI agents call compare_players 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 retrieves and displays player statistics and information for comparison without modifying, deleting, or executing operations. It has no side effects on the FPL system or user data. The blast radius of misuse is minimal—worst case an AI agent would request comparisons of irrelevant players, wasting compute resources but causing no harm. This is a straightforward Read operation.
From the tool's definition Tool name 'compare_players' and description 'Compare multiple players side-by-side using their names' indicates a retrieval/query operation that retrieves and presents existing player data for comparison purposes.
Attacks that exploit this kind of access
Compare multiple players side-by-side using their names. 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 compare_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 FPL MCP Server. Nothing to install.
compare_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 compare_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 compare_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.
compare_players 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 →