AI agents call perps_auth_status to retrieve information from Logiqical 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 query to check the status of authentication steps. It retrieves data about a user's authentication progress without creating, modifying, deleting, or executing any actions. The low severity reflects that exposing authentication status information has minimal blast radius—it does not grant fund access, execute trades, or make irreversible changes.
From the tool's definition Tool name 'perps_auth_status' and description 'Check which auth steps are completed for perps' indicate a status query operation that retrieves information about authentication completion state without modifying data or executing transactions.
Attacks that exploit this kind of access
Check which auth steps are completed for perps. It is categorised as a Read tool in the Logiqical MCP Server, which means it retrieves data without modifying state.
Register the Logiqical MCP server in PolicyLayer and add a rule for perps_auth_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 Logiqical. Nothing to install.
perps_auth_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 perps_auth_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 perps_auth_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.
perps_auth_status is provided by the Logiqical MCP server (logiqical-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 →