list_scenes
List all .scene files in the project with their paths and basic metadata
This record as markdown: /tools/sbox/list-scenes.md
What list_scenes does on Sbox
AI agents call list_scenes to retrieve information from Sbox without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_scenes is rated Low
This tool retrieves information about existing scene files without creating, modifying, deleting, or executing operations. It is a straightforward query operation with minimal risk if misused by an AI agent, as it only exposes file paths and metadata already present in the project.
From the tool's definition Tool name 'list_scenes' and description 'List all .scene files in the project with their paths and basic metadata' indicate data retrieval only. The verb 'list' and the read-only nature of querying file metadata confirm no side effects.
Attacks that exploit this kind of access
The rule that runs list_scenes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sbox, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_scenes, this is the rule to start with:
list_scenes 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 Sbox, apply this rule, and every list_scenes call is checked against it from then on.
Questions about list_scenes
List all .scene files in the project with their paths and basic metadata. It is categorised as a Read tool in the Sbox MCP Server, which means it retrieves data without modifying state.
Register the Sbox MCP server in PolicyLayer and add a rule for list_scenes: 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 Sbox. Nothing to install.
list_scenes 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 list_scenes 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 list_scenes. 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.
list_scenes is provided by the Sbox MCP server (sbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sbox, and thousands of servers like it.
This server
Across the catalogue