set_project_root
Switch the active project memory database to the given absolute project path. Use at session start when the server was launched outside the project directory
This record as markdown: /tools/1999azzar-project-guardian-mcp-server/set-project-root.md
What set_project_root does on Project Guardian MCP
AI agents use set_project_root to create or update resources in Project Guardian MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Project Guardian MCP environment.
Why set_project_root is rated Medium
Tool modifies application state by redirecting database operations to different project contexts, affecting subsequent tool behavior.
From the tool's definition Switch active project memory database to given absolute project path.
Attacks that exploit this kind of access
The rule that runs set_project_root safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Project Guardian MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_project_root, this is the rule to start with:
set_project_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Project Guardian MCP, apply this rule, and every set_project_root call is checked against it from then on.
Questions about set_project_root
Switch the active project memory database to the given absolute project path. Use at session start when the server was launched outside the project directory. It is categorised as a Write tool in the Project Guardian MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Project Guardian MCP server in PolicyLayer and add a rule for set_project_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 Project Guardian MCP. Nothing to install.
set_project_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 set_project_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 set_project_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.
set_project_root is provided by the Project Guardian MCP server (1999azzar/project-guardian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Project Guardian, and thousands of servers like it.
This server
Across the catalogue