Get your current team squad, chips status, and transfer information.
AI agents call get_my_squad 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 queries and returns information about the user's Fantasy Premier League team state. No data is created, modified, deleted, or overwritten. No code is executed, no external operations are triggered, and no financial transactions occur. The blast radius of misuse is minimal—an attacker could only view the user's squad composition and transfer status, not modify their team or commit financial resources.
From the tool's definition Tool description states 'Get your current team squad, chips status, and transfer information' — purely retrieves data about the user's existing squad without modifying or triggering any actions.
Attacks that exploit this kind of access
Get your current team squad, chips status, and transfer information. 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_my_squad: 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_my_squad 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_my_squad 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_my_squad. 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_my_squad 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 →