Step 2: Checks if the user has completed the web login.
AI agents call check_login_status 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 is a read-only operation that queries login state. It has no capacity to modify data, execute code, trigger external actions irreversibly, or move money. The blast radius of misuse is minimal—an AI agent checking login status cannot cause harm beyond retrieving information about whether authentication is complete.
From the tool's definition Tool name is 'check_login_status' and description states it 'Checks if the user has completed the web login.' This retrieves the current authentication status without modifying, executing operations, or causing side effects.
Attacks that exploit this kind of access
Step 2: Checks if the user has completed the web login. 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 check_login_status: 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.
check_login_status 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 check_login_status 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 check_login_status. 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.
check_login_status 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 →