analyze_squad_recent_performance
AI agents call analyze_squad_recent_performance 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.
The tool analyzes historical performance metrics, which is a retrieval operation with no side effects. It gathers data to inform decision-making but does not create, modify, delete, or execute external operations. While the description is empty, lowering confidence slightly, the naming convention and server context strongly suggest it is a Read operation consistent with other non-destructive FPL API queries.
From the tool's definition Tool name 'analyze_squad_recent_performance' indicates retrieval and analysis of historical performance data.
Attacks that exploit this kind of access
analyze_squad_recent_performance. 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 analyze_squad_recent_performance: 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.
analyze_squad_recent_performance 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 analyze_squad_recent_performance 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 analyze_squad_recent_performance. 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.
analyze_squad_recent_performance 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 →