update_backlog_item

THE RISK

Medium Risk

Why update_backlog_item needs a policy

This tool modifies existing data (backlog items) in a reversible way — it changes metadata like priority, title, tags, or phase. No code execution, deletion, or financial operations are involved. Misuse could corrupt backlog prioritization or task metadata, hence medium severity.

From the tool's definition Updates an item in BACKLOG.md. Can change priority, title, tags, or phase without promoting to active work.

Documented attack patterns abuse exactly the kind of access update_backlog_item gives an agent:

POLICY

How to control update_backlog_item

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 update_backlog_item:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_backlog_item": {
      "limits": [
        {
          "counter": "update_backlog_item_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

update_backlog_item 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.

Create a free account and register Project MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Project MCP tools

Destructive delete_task Permanently deletes a task from todos/. Use with caution - this cannot be undone. Consider Destructive remove_from_backlog Removes an item from BACKLOG.md without promoting it. Use for tasks that are no longer nee Execute lint_project_docs Validates project documentation against standards. Checks for required files, valid frontm Write init_project Initializes the .project/ directory with all standard files following strict templates. Cr Write sync_todo_index Syncs the parent TODO.md file with all tasks. Generates a dashboard view with tasks organi Write add_decision Adds a single architecture decision record (ADR) to DECISIONS.md. Creates a structured ent Write add_roadmap_milestone Adds a milestone or phase to ROADMAP.md. Creates a structured entry with title, descriptio Write add_to_backlog Adds a single item to BACKLOG.md. Use this for quick task creation without bulk import. It

All 42 Project MCP tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about update_backlog_item

What does the update_backlog_item tool do? +

Updates an item in BACKLOG.md. Can change priority, title, tags, or phase without promoting 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.

How do I enforce a policy on update_backlog_item? +

Register the Project MCP server in PolicyLayer and add a rule for update_backlog_item: 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.

What risk level is update_backlog_item? +

update_backlog_item is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_backlog_item? +

Yes. Add a rate_limit block to the update_backlog_item 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.

How do I block update_backlog_item completely? +

Set action: deny in the PolicyLayer policy for update_backlog_item. 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.

What MCP server provides update_backlog_item? +

update_backlog_item 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.

Enforce policy on every Project MCP tool call.

Start from Project MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →