Adds a single item to BACKLOG.md. Use this for quick task creation without bulk import. Items are added to the specified priority section and can later be promoted to active work.
AI agents use add_to_backlog 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.
This tool creates new data (backlog items) in a reversible manner. It does not execute external operations, delete data, move money, or trigger irreversible changes. The modification is additive and can be undone by removing the item later.
From the tool's definition Tool description states it 'Adds a single item to BACKLOG.md' and 'Items are added to the specified priority section', indicating creation of new task data in a persistent file.
Documented attack patterns abuse exactly the kind of access add_to_backlog 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 add_to_backlog:
{
"version": "1",
"default": "deny",
"tools": {
"add_to_backlog": {
"limits": [
{
"counter": "add_to_backlog_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_to_backlog 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.
Adds a single item to BACKLOG.md. Use this for quick task creation without bulk import. Items are added to the specified priority section and can later be promoted to active work. 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 add_to_backlog: 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.
add_to_backlog 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 add_to_backlog 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 add_to_backlog. 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.
add_to_backlog 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.