AI agents use set_project_directory to create or update resources in MCP File Edit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP File Edit environment.
Based on the name, this tool likely sets or changes the active project directory context for the server. This is a Write/configuration operation — it modifies server state — but the empty description significantly reduces confidence. It doesn't appear destructive or financial. Severity is medium because changing the working directory could affect subsequent operations performed by the agent.
From the tool's definition Tool name 'set_project_directory'; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access set_project_directory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP File Edit, and nothing reaches the server without passing your rules. This is the rule we recommend for set_project_directory:
{
"version": "1",
"default": "deny",
"tools": {
"set_project_directory": {
"limits": [
{
"counter": "set_project_directory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_project_directory 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_directory. It is categorised as a Write tool in the MCP File Edit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP File Edit MCP server in PolicyLayer and add a rule for set_project_directory: 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 MCP File Edit. Nothing to install.
set_project_directory 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_directory 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_directory. 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_directory is provided by the MCP File Edit MCP server (patrickomatik/mcp-file-edit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP File Edit, 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.
32 MCP File Edit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.