Fetch all FPL fixtures
AI agents call getFixtures 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 fixture data from the Fantasy Premier League API. It performs a query operation that reads and returns information about FPL fixtures without creating, modifying, deleting, or executing any operations. The data returned is static fixture information used for informational purposes only. This is a straightforward read operation with minimal security risk.
From the tool's definition Tool name is 'getFixtures' and description states 'Fetch all FPL fixtures' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Fetch all FPL fixtures. 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 getFixtures: 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.
getFixtures 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 getFixtures 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 getFixtures. 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.
getFixtures 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 →