Low Risk

get_epic_progress

get_epic_progress

How to control get_epic_progress ↓

What get_epic_progress does on Kanban

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

Low Risk

Why get_epic_progress needs a policy

The tool name strongly suggests it retrieves or queries epic progress data without modifying state. While the description is empty (limiting confidence), the naming convention and context within a kanban system indicate this is a data retrieval operation with no side effects. Read operations have low severity as they do not alter system state or enable destructive actions.

From the tool's definition Tool name 'get_epic_progress' indicates retrieval of progress metrics or status information for epics, with no mutation keywords (no add/edit/delete/close). The 'get_' prefix is a strong signal of a read-only query operation.

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

How to control get_epic_progress

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

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

get_epic_progress 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 Kanban — 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.

Related tools and policies

Go deeper

Questions about get_epic_progress

What does the get_epic_progress tool do? +

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

How do I enforce a policy on get_epic_progress? +

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

What risk level is get_epic_progress? +

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

Can I rate-limit get_epic_progress? +

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

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

get_epic_progress is provided by the Kanban MCP server (multidimensionalcats/kanban-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kanban tool call.

Start from Kanban, 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.

45 Kanban tools catalogued and risk-classified — across an index of 43,000+ 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.