Switch the active workspace for this session. Tool descriptions prefixed [ws1]/[ws2] show which workspace each tool belongs to; after switching, the tool list refreshes to show the new workspace
AI agents use switchWorkspace to create or update resources in Patchwork Os — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Patchwork Os environment.
Switching the active workspace modifies session state (which workspace is currently active) and causes the tool list to refresh. This is a reversible state change with no data deletion or financial implications. Severity is medium because misuse could redirect AI operations to an unintended workspace, affecting subsequent tool calls.
From the tool's definition Switch the active workspace for this session... after switching, the tool list refreshes to show the new workspace
Documented attack patterns abuse exactly the kind of access switchWorkspace gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Patchwork Os, and nothing reaches the server without passing your rules. This is the rule we recommend for switchWorkspace:
{
"version": "1",
"default": "deny",
"tools": {
"switchWorkspace": {
"limits": [
{
"counter": "switchworkspace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}switchWorkspace 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.
Free to start. No card required.
Switch the active workspace for this session. Tool descriptions prefixed [ws1]/[ws2] show which workspace each tool belongs to; after switching, the tool list refreshes to show the new workspace. It is categorised as a Write tool in the Patchwork Os MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Patchwork Os MCP server in PolicyLayer and add a rule for switchWorkspace: 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 Patchwork Os. Nothing to install.
switchWorkspace is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the switchWorkspace 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 switchWorkspace. 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.
switchWorkspace is provided by the Patchwork Os MCP server (oolab-labs/patchwork-os). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Patchwork Os, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Patchwork Os tools catalogued and risk-classified — across an index of 43,000+ MCP servers.