New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

permissions_list_open

List open OpenClaw exec or plugin approval requests visible through the Gateway.

SERVEROpenClaw SOURCEopenclaw
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity verified Pull the record →

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.

Questions about permissions_list_open

What does the permissions_list_open tool do? +

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.

How do I enforce a policy on permissions_list_open? +

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.

What risk level is permissions_list_open? +

permissions_list_open is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit permissions_list_open? +

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.

How do I block permissions_list_open completely? +

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.

What MCP server provides permissions_list_open? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of OpenClaw's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.