Fetch all transfers of a team
AI agents call getEntryTransfers 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 historical transfer data for a Fantasy Premier League team entry. It queries existing information from the FPL API without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an attacker could only view transfer history, which is typically public or restricted to team ownership.
From the tool's definition Tool name 'getEntryTransfers' and description 'Fetch all transfers of a team' indicate data retrieval with no modification capability. The verb 'fetch' explicitly denotes a read-only operation.
Attacks that exploit this kind of access
Fetch all transfers of a team. 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 getEntryTransfers: 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.
getEntryTransfers 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 getEntryTransfers 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 getEntryTransfers. 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.
getEntryTransfers is provided by the FPL MCP Server MCP server (owen-lacey/fpl-mcp). 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 →