runbox_list_directory
List all direct children in a directory in an existing code sandbox, non recursive, linux debian VM
This record as markdown: /tools/11cafe-website-publisher-mcp/runbox-list-directory.md
What runbox_list_directory does on Runbox Website Builder MCP
AI agents call runbox_list_directory to retrieve information from Runbox Website Builder MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why runbox_list_directory is rated Low
This tool only retrieves directory contents without side effects, matching the Read category definition. The blast radius is minimal: exposure of this tool allows an attacker to discover file structure but cannot modify, delete, or execute code. Severity is low because directory enumeration alone presents limited risk compared to write, execute, or destructive operations on the same server.
From the tool's definition Tool name contains 'list' and description states 'List all direct children in a directory' — core read operation with no modification or execution capability. The non-recursive scope and read-only nature further confirm this.
Attacks that exploit this kind of access
The rule that runs runbox_list_directory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Runbox Website Builder MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For runbox_list_directory, this is the rule to start with:
runbox_list_directory 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 Runbox Website Builder MCP, apply this rule, and every runbox_list_directory call is checked against it from then on.
Questions about runbox_list_directory
List all direct children in a directory in an existing code sandbox, non recursive, linux debian VM. It is categorised as a Read tool in the Runbox Website Builder MCP MCP Server, which means it retrieves data without modifying state.
Register the Runbox Website Builder MCP server in PolicyLayer and add a rule for runbox_list_directory: 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 Runbox Website Builder MCP. Nothing to install.
runbox_list_directory 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 runbox_list_directory 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 runbox_list_directory. 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.
runbox_list_directory is provided by the Runbox Website Builder MCP server (11cafe/website-publisher-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Runbox Website Builder, and thousands of servers like it.
This server
Across the catalogue