permissions_list_open
List open OpenClaw exec or plugin approval requests visible through the Gateway.
This record as markdown: /tools/openclaw/permissions-list-open.md
What permissions_list_open does on OpenClaw
AI agents call permissions_list_open 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 permissions_list_open is rated Low
This tool queries and retrieves existing approval request data visible through the Gateway. It performs a read-only list operation on approval requests, returning information about pending approvals without modifying, executing, or deleting any data. The low severity reflects that accessing approval metadata poses minimal risk—it reveals what requests are pending but does not approve, modify, or execute them.
From the tool's definition Tool name and description indicate 'List open...approval requests' - a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs permissions_list_open 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 permissions_list_open, this is the rule to start with:
permissions_list_open 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 permissions_list_open call is checked against it from then on.
Questions about permissions_list_open
List open OpenClaw exec or plugin approval requests visible through the Gateway. 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 permissions_list_open: 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.
permissions_list_open 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 permissions_list_open 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 permissions_list_open. 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.
permissions_list_open 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