remove_from_backlog

THE RISK

Critical Risk

Why remove_from_backlog needs a policy

The tool permanently removes an item from the backlog without any promotion or archival path, making it an irreversible deletion of project task data. There is no indication of recovery or undo capability, fitting the Destructive category.

From the tool's definition Removes an item from BACKLOG.md without promoting it... tasks that are no longer needed or were added by mistake

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

POLICY

How to control remove_from_backlog

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_from_backlog"
  ]
}

remove_from_backlog disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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.

RESTRICT 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 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 Write archive_task Archives a completed task by moving it from todos/ to archive/. Keeps the active task queu

All 42 Project MCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Project MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about remove_from_backlog

What does the remove_from_backlog tool do? +

Removes an item from BACKLOG.md without promoting it. Use for tasks that are no longer needed or were added by mistake. It is categorised as a Destructive tool in the Project MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_from_backlog? +

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

What risk level is remove_from_backlog? +

remove_from_backlog is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_from_backlog? +

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

How do I block remove_from_backlog completely? +

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

What MCP server provides remove_from_backlog? +

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

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 →