Verificar status das sessões do OpenClaw
AI agents call sessions_status to retrieve information from OpenClaw MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool checks the status of existing sessions, which is a purely informational retrieval operation with no side effects, data modification, or execution capabilities. It presents minimal security risk as it does not create, modify, delete, or execute any operations—only returns current session state.
From the tool's definition Tool name 'sessions_status' and description 'Verificar status das sessões do OpenClaw' (Verify status of OpenClaw sessions) indicate a read-only query operation that retrieves session state information without modification.
Attacks that exploit this kind of access
Verificar status das sessões do OpenClaw. It is categorised as a Read tool in the OpenClaw MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenClaw MCP Server MCP server in PolicyLayer and add a rule for sessions_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 OpenClaw MCP Server. Nothing to install.
sessions_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 sessions_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 sessions_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.
sessions_status is provided by the OpenClaw MCP Server MCP server (rodgco/openclaw-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 →