Low Risk

list_epics

list_epics

How to control list_epics ↓

AI agents call list_epics to retrieve information from Taiga MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The 'list' prefix is a strong signal of a read-only operation that retrieves data without modification or side effects. The sibling tools on this server (add_comment, assign_*, create_*, bulk_create_*, bulk_update_*) are all write/execute operations, which further confirms this tool's read-only nature. No destructive, financial, or execute operations are implied.

From the tool's definition Tool name 'list_epics' clearly indicates a retrieval operation that queries and returns epic data from Taiga. The name follows standard read operation naming conventions (list/get/fetch).

Documented attack patterns abuse exactly the kind of access list_epics 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 list_epics:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_epics": {}
  }
}

list_epics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the list_epics tool do? +

list_epics. It is categorised as a Read tool in the Taiga MCP Bridge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_epics? +

Register the Taiga MCP Bridge MCP server in PolicyLayer and add a rule for list_epics: 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 list_epics? +

list_epics is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_epics? +

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

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

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