This record as markdown: /tools/agentics-ai-code-mcp/set-workspace.md
What set_workspace does on Code MCP Server
AI agents use set_workspace to create or update resources in Code MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Code MCP Server environment.
Why set_workspace is rated Medium
This tool changes configuration state (the active workspace) rather than permanently destroying data. While it affects the execution context of other tools, the change itself is reversible—another set_workspace call can restore the previous state. This makes it a Write operation.
From the tool's definition Tool name is 'set_workspace' and description states 'Set the active workspace directory' — this modifies the state of the active workspace configuration, which is a reversible change affecting subsequent tool operations.
Attacks that exploit this kind of access
The rule that runs set_workspace safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Code MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_workspace, this is the rule to start with:
set_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Code MCP Server, apply this rule, and every set_workspace call is checked against it from then on.
Questions about set_workspace
Set the active workspace directory. It is categorised as a Write tool in the Code MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Code MCP Server MCP server in PolicyLayer and add a rule for set_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 Code MCP Server. Nothing to install.
set_workspace 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 set_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.
Set action: deny in the PolicyLayer policy for set_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.
set_workspace is provided by the Code MCP Server MCP server (agentics-ai/code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Code MCP Server, and thousands of servers like it.
This server
Across the catalogue