vibecontrols_sandboxes_list

List sandboxes in the current workspace with optional template/status filters.

SERVERVibecontrols SOURCE@vibecontrols/mcp

Low RISK CLASS

Category Read

Parameters 50 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/vibecontrols-mcp/vibecontrols-sandboxes-list.md

WHAT IT DOES

What vibecontrols_sandboxes_list does on Vibecontrols

AI agents call vibecontrols_sandboxes_list to retrieve information from Vibecontrols without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required
`page`	number	—
`limit`	number	—
`offset`	number	—
`status`	string	—
`template`	string	—

Parameters from the server's own tool schema.

RISK

Why vibecontrols_sandboxes_list is rated Low

Even though vibecontrols_sandboxes_list only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsAccepts raw HTML/template content (template)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vibecontrols_sandboxes_list safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Vibecontrols, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vibecontrols_sandboxes_list, this is the rule to start with:

vibecontrols_sandboxes_list Allowed

vibecontrols_sandboxes_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vibecontrols_sandboxes_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vibecontrols, apply this rule, and every vibecontrols_sandboxes_list call is checked against it from then on.

FAQ

Questions about vibecontrols_sandboxes_list

What does the vibecontrols_sandboxes_list tool do? +

List sandboxes in the current workspace with optional template/status filters. It is categorised as a Read tool in the Vibecontrols MCP Server, which means it retrieves data without modifying state.

What parameters does vibecontrols_sandboxes_list accept? +

vibecontrols_sandboxes_list accepts 5 parameters: page, limit, offset, status, template. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on vibecontrols_sandboxes_list? +

Register the Vibecontrols MCP server in PolicyLayer and add a rule for vibecontrols_sandboxes_list: 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 Vibecontrols. Nothing to install.

What risk level is vibecontrols_sandboxes_list? +

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

Can I rate-limit vibecontrols_sandboxes_list? +

Yes. Add a rate_limit block to the vibecontrols_sandboxes_list 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 vibecontrols_sandboxes_list completely? +

Set action: deny in the PolicyLayer policy for vibecontrols_sandboxes_list. 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 vibecontrols_sandboxes_list? +

vibecontrols_sandboxes_list is provided by the Vibecontrols MCP server (@vibecontrols/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vibecontrols, and thousands of servers like it.

This server

All 672 Vibecontrols tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →