Search for all players from a specific team by team name.
AI agents call search_players_by_team 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 performs a read-only search operation against the FPL API to retrieve player information filtered by team. It has no side effects, does not execute external commands, does not modify data, and does not involve financial transactions. The low severity reflects minimal risk even if misused—returning player roster information is informational only and cannot harm FPL accounts or data integrity.
From the tool's definition Tool name 'search_players_by_team' and description 'Search for all players from a specific team by team name' indicate a query/lookup operation that retrieves player data without modifying or deleting anything.
Attacks that exploit this kind of access
Search for all players from a specific team by team name. 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 search_players_by_team: 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.
search_players_by_team 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 search_players_by_team 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 search_players_by_team. 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.
search_players_by_team 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 →