Check the status of the local Chrome session.
AI agents call local_session_status to retrieve information from Squidlerio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns information about an existing Chrome session state without creating, modifying, executing, deleting, or committing any resources. It is a basic informational read operation with minimal blast radius if misused by an AI agent.
From the tool's definition The tool description explicitly states it checks/retrieves the status of the local Chrome session with no modification or execution capability. The verb 'check' and the action of querying status is a read-only operation with no side effects.
Attacks that exploit this kind of access
Check the status of the local Chrome session. It is categorised as a Read tool in the Squidlerio MCP Server, which means it retrieves data without modifying state.
Register the Squidlerio MCP server in PolicyLayer and add a rule for local_session_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 Squidlerio. Nothing to install.
local_session_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 local_session_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 local_session_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.
local_session_status is provided by the Squidlerio MCP server (squidlerio/squidler-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 →