Change the project workspace path at runtime. Use this when you detect the current workspace is incorrect or you need to switch to a different project directory. Creates cache folder automatically and optionally re-indexes the new workspace.
AI agents use e_set_workspace to create or update resources in Smart Coding MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Smart Coding MCP environment.
This tool modifies system state by changing workspace paths and creating cache directories. While not destructive (changes are reversible by resetting workspace), it goes beyond reading data and constitutes a Write operation that alters application configuration and filesystem structures.
From the tool's definition The tool "Change the project workspace path at runtime" and "Creates cache folder automatically and optionally re-indexes the new workspace" indicates it modifies runtime configuration state and filesystem structures (cache folder creation).
Documented attack patterns abuse exactly the kind of access e_set_workspace gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Smart Coding MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for e_set_workspace:
{
"version": "1",
"default": "deny",
"tools": {
"e_set_workspace": {
"limits": [
{
"counter": "e_set_workspace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}e_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.
Free to start. No card required.
Change the project workspace path at runtime. Use this when you detect the current workspace is incorrect or you need to switch to a different project directory. Creates cache folder automatically and optionally re-indexes the new workspace. It is categorised as a Write tool in the Smart Coding MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Smart Coding MCP server in PolicyLayer and add a rule for e_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 Smart Coding MCP. Nothing to install.
e_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 e_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 e_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.
e_set_workspace is provided by the Smart Coding MCP server (omar-haris/smart-coding-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Smart Coding MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Smart Coding MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.