vibecontrols_workspace_list
List workspaces visible to the current actor on the workspace gateway, with optional filters and pagination. Returns { items, total, hasMore }.
This record as markdown: /tools/vibecontrols-mcp/vibecontrols-workspace-list.md
What vibecontrols_workspace_list does on Vibecontrols
AI agents call vibecontrols_workspace_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 | Description |
|---|---|---|---|
limit | integer | — | Page size (default 100) |
orgId | string | — | Filter by organization ID |
offset | integer | — | Pagination offset (default 0) |
search | string | — | Free-text search across name/slug/description |
status | string | — | Filter by workspace status (will be uppercased; e.g. ACTIVE|ARCHIVED) |
tenantId | string | — | Filter by tenant ID |
Parameters from the server's own tool schema.
Why vibecontrols_workspace_list is rated Low
Even though vibecontrols_workspace_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.
Attacks that exploit this kind of access
The rule that runs vibecontrols_workspace_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_workspace_list, this is the rule to start with:
vibecontrols_workspace_list 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 Vibecontrols, apply this rule, and every vibecontrols_workspace_list call is checked against it from then on.
Questions about vibecontrols_workspace_list
List workspaces visible to the current actor on the workspace gateway, with optional filters and pagination. Returns { items, total, hasMore }. It is categorised as a Read tool in the Vibecontrols MCP Server, which means it retrieves data without modifying state.
vibecontrols_workspace_list accepts 6 parameters: limit, orgId, offset, search, status, tenantId. The full parameter table on this page comes from the server's own tool schema.
Register the Vibecontrols MCP server in PolicyLayer and add a rule for vibecontrols_workspace_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.
vibecontrols_workspace_list 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 vibecontrols_workspace_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.
Set action: deny in the PolicyLayer policy for vibecontrols_workspace_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.
vibecontrols_workspace_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.
More on Vibecontrols, and thousands of servers like it.
This server
Across the catalogue