Critical Risk →

delete_epic

delete_epic

How to control delete_epic ↓

AI agents call delete_epic to permanently remove resources in Taiga MCP Bridge — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Deletion of epics in a project management system irreversibly removes work item records and associated metadata. This cannot be undone without recovery procedures, fitting the Destructive category.

From the tool's definition Tool name is 'delete_epic' which explicitly indicates deletion of epics—irreversible data removal. The sibling tools include create, assign, and bulk operations on project management artifacts (epics, tasks, user stories, sprints), and this tool's name…

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

PolicyLayer is an MCP gateway — it sits between your AI agents and Taiga MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_epic:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_epic"
  ]
}

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

  1. Create a free account and register Taiga MCP Bridge — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete_epic tool do? +

delete_epic. It is categorised as a Destructive tool in the Taiga MCP Bridge 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 delete_epic? +

Register the Taiga MCP Bridge MCP server in PolicyLayer and add a rule for delete_epic: 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 Taiga MCP Bridge. Nothing to install.

What risk level is delete_epic? +

delete_epic 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 delete_epic? +

Yes. Add a rate_limit block to the delete_epic 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 delete_epic completely? +

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

delete_epic is provided by the Taiga MCP Bridge MCP server (talhaorak/pytaiga-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Taiga MCP Bridge tool call.

Deterministic rules across all 94 Taiga MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

94 Taiga MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.