list_sandboxes
List the sandbox linked to the current workspace (one sandbox per workspace). Each entry includes the sandbox link id, status (creating/active/refreshing/failed/deleting), the sandbox workspace code, and copy stats. Operates on the current workspace; use switch_workspace first if needed.
This record as markdown: /tools/sankahq-sanka-mcp/list-sandboxes.md
What list_sandboxes does on Sanka MCP Server
AI agents call list_sandboxes to retrieve information from Sanka MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_sandboxes is rated Low
This tool retrieves and queries sandbox information without any side effects or modifications to data. It returns read-only metadata about sandboxes associated with the current workspace. The operation is non-destructive and produces no irreversible changes, placing it squarely in the Read category with low severity.
From the tool's definition Tool performs a 'list' operation that 'List the sandbox linked to the current workspace' with descriptive retrieval of metadata including 'sandbox link id, status, sandbox workspace code, and copy stats.' No modifications, deletions, or command execution…
Attacks that exploit this kind of access
The rule that runs list_sandboxes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_sandboxes, this is the rule to start with:
list_sandboxes 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 Sanka MCP Server, apply this rule, and every list_sandboxes call is checked against it from then on.
Questions about list_sandboxes
List the sandbox linked to the current workspace (one sandbox per workspace). Each entry includes the sandbox link id, status (creating/active/refreshing/failed/deleting), the sandbox workspace code, and copy stats. Operates on the current workspace; use switch_workspace first if needed. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for list_sandboxes: 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 Sanka MCP Server. Nothing to install.
list_sandboxes 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_sandboxes 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_sandboxes. 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_sandboxes is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue