Add a directory to the allowed whitelist.
AI agents use set_root_path to create or update resources in Code Editor MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Code Editor MCP Server environment.
An AI agent can call set_root_path faster than any human can review — one bad instruction and it creates or modifies resources in Code Editor MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Add a directory to the allowed whitelist. It is categorised as a Write tool in the Code Editor MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Code Editor MCP Server MCP server in PolicyLayer and add a rule for set_root_path: 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 Editor MCP Server. Nothing to install.
set_root_path 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_root_path 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_root_path. 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_root_path is provided by the Code Editor MCP Server MCP server (tripqi/code-editor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.