Smart tool that automatically determines which project file to create or update based on context. Use this when making changes to the project - it will check project state and determine if index.md, ROADMAP.md, TODO.md, STATUS.md, or DECISIONS.md should be created/updated. This is the primary too...
AI agents use manage_project_file to create or update resources in Project MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Project MCP environment.
The tool modifies project documentation files in a reversible manner. While it can create or update multiple critical project files, it does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely read data (Read).
From the tool's definition Tool description explicitly states it will 'create or update' project files including index.md, ROADMAP.md, TODO.md, STATUS.md, and DECISIONS.md.
Documented attack patterns abuse exactly the kind of access manage_project_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Project MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_project_file:
{
"version": "1",
"default": "deny",
"tools": {
"manage_project_file": {
"limits": [
{
"counter": "manage_project_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_project_file 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.
Smart tool that automatically determines which project file to create or update based on context. Use this when making changes to the project - it will check project state and determine if index.md, ROADMAP.md, TODO.md, STATUS.md, or DECISIONS.md should be created/updated. This is the primary tool for managing project documentation during development. It is categorised as a Write tool in the Project MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Project MCP server in PolicyLayer and add a rule for manage_project_file: 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 MCP. Nothing to install.
manage_project_file 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 manage_project_file 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 manage_project_file. 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.
manage_project_file is provided by the Project MCP server (pouyanafisi/project-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Project MCP, 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.
42 Project MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.