Set PROJECT_ROOT at runtime to target another folder (e.g., 8th Wall Desktop project)
AI agents use project_set_root to create or update resources in 8th Wall MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 8th Wall MCP Server environment.
This tool modifies the PROJECT_ROOT environment variable at runtime, which is a configuration change. While reversible (can be set back to the original value), it redirects all subsequent tool operations to a different directory, potentially affecting file I/O and project context for other tools on the server.
From the tool's definition Tool name 'project_set_root' and description 'Set PROJECT_ROOT at runtime to target another folder' indicates modifying a runtime configuration/environment variable that affects which project directory is targeted.
Documented attack patterns abuse exactly the kind of access project_set_root gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and 8th Wall MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for project_set_root:
{
"version": "1",
"default": "deny",
"tools": {
"project_set_root": {
"limits": [
{
"counter": "project_set_root_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}project_set_root 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.
Set PROJECT_ROOT at runtime to target another folder (e.g., 8th Wall Desktop project). It is categorised as a Write tool in the 8th Wall MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 8th Wall MCP Server MCP server in PolicyLayer and add a rule for project_set_root: 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 8th Wall MCP Server. Nothing to install.
project_set_root 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 project_set_root 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 project_set_root. 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.
project_set_root is provided by the 8th Wall MCP Server MCP server (superdwayne/8thwallmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from 8th Wall MCP Server, 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.
64 8th Wall MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.