workspace_switch

SERVERDialogbrain SOURCEhttps://api.dialogbrain.com/mcp

High RISK CLASS

Category Execute

Parameters 20 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-saloprj-dialogbrain/workspace-switch.md

WHAT IT DOES

What workspace_switch does on Dialogbrain

AI agents invoke workspace_switch to trigger actions in Dialogbrain. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`slug`	string	—	Workspace slug to switch to. Resolved within the caller's memberships, so cross-tenant slug collisions are not possible. Mutually exclusive with `workspace_id`.
`workspace_id`	integer	—	Numeric workspace id to switch to. Mutually exclusive with `slug`.

Parameters from the server's own tool schema.

RISK

Why workspace_switch is rated High

This tool modifies the active execution context/session by switching which workspace all subsequent tool calls operate against. It triggers an external state change (re-pointing the API key) that affects all following operations.

From the tool's definition Re-point the active MCP API key to a different workspace... Takes effect on the very next tool call

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs workspace_switch safely

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

workspace_switch Rate-limited

workspace_switch stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "workspace_switch": {
      "limits": [
        {
          "counter": "workspace_switch_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about workspace_switch

What does the workspace_switch tool do? +

Re-point the active MCP API key to a different workspace. Pass exactly one of workspace_id or slug (find them via workspace.list). Takes effect on the very next tool call — no MCP reconnect, no new API key. Sequential checkpoint: do not parallelize tool calls across a switch — calls already in flight when the switch commits will run against the previous workspace. It is categorised as a Execute tool in the Dialogbrain MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does workspace_switch accept? +

workspace_switch accepts 2 parameters: slug, workspace_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on workspace_switch? +

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

What risk level is workspace_switch? +

workspace_switch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit workspace_switch? +

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

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

workspace_switch is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Dialogbrain, and thousands of servers like it.

This server

All 223 Dialogbrain tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →