compare_managers
AI agents call compare_managers 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.
Based on naming convention and server context (competitor analysis, research functions), this tool most likely retrieves and compares manager data without modifying or executing actions. The empty description reduces confidence slightly, but the pattern of sibling tools and stated purpose (analysis/research) strongly indicates Read category. No evidence of side effects, state changes, or financial implications.
From the tool's definition Tool name 'compare_managers' with no description; context shows server is for 'player research, competitor analysis' suggesting read-only operations. Sibling tools like 'analyze_squad_recent_performance', 'compare_players', 'find_player' are all Read category.
Attacks that exploit this kind of access
compare_managers. 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_managers: 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_managers 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_managers 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_managers. 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_managers 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 →