switch_workspace · Sidvy MCP Server MCP: Risk & Policy

WHAT IT DOES

What switch_workspace does on Sidvy MCP Server

AI agents use switch_workspace to create or update resources in Sidvy MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sidvy MCP Server environment.

WHY IT NEEDS A POLICY

Why switch_workspace needs a policy

This tool changes application state (the active workspace context) for subsequent operations. While it does not create, modify, or delete data directly, it alters which workspace will be affected by follow-up operations, making it a Write-category tool.

From the tool's definition "Switch context to a different workspace" indicates a state-changing operation that modifies the active workspace context for subsequent operations, which is a contextual write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

switch_workspace Rate-limited

switch_workspace stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "switch_workspace": {
      "limits": [
        {
          "counter": "switch_workspace_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sidvy MCP Server, so you can run agents against it safely.

FAQ

Questions about switch_workspace

What does the switch_workspace tool do? +

Switch context to a different workspace (for subsequent operations). It is categorised as a Write tool in the Sidvy MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on switch_workspace? +

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

What risk level is switch_workspace? +

switch_workspace is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit switch_workspace? +

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

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

switch_workspace is provided by the Sidvy MCP Server MCP server (martinhjartmyr/sidvy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.