This record as markdown: /tools/openclaw/gateway-status.md
What gateway-status does on OpenClaw
AI agents call gateway-status to retrieve information from OpenClaw without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why gateway-status is rated Low
This tool retrieves and displays status information about a gateway. The verb 'show' and the context of a 'summary' are consistent with read-only operations that have no side effects. There is no indication of any data modification, deletion, execution of commands, or financial operations. The low severity reflects that status information disclosure has minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'gateway-status' and description 'Show gateway status summary' indicate a query/retrieval operation that displays status information without modifying any state.
Attacks that exploit this kind of access
The rule that runs gateway-status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and OpenClaw, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gateway-status, this is the rule to start with:
gateway-status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect OpenClaw, apply this rule, and every gateway-status call is checked against it from then on.
Questions about gateway-status
Show gateway status summary. It is categorised as a Read tool in the OpenClaw MCP Server, which means it retrieves data without modifying state.
Register the OpenClaw MCP server in PolicyLayer and add a rule for gateway-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. Nothing to install.
gateway-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 gateway-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 gateway-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.
gateway-status is provided by the OpenClaw MCP server (openclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on OpenClaw, and thousands of servers like it.
This server
Across the catalogue