AI agents use assign_epic_to_user to create or update resources in Taiga MCP Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Taiga MCP Bridge environment.
This tool creates or modifies project metadata (epic assignments) reversibly within Taiga's project management system. It does not delete data, execute arbitrary code, or move money, so it falls under Write. Severity is medium because assigning epics could affect project planning and resource allocation, but the action is reversible and affects only metadata within a bounded project context.
From the tool's definition Tool name 'assign_epic_to_user' indicates modification of epic ownership/assignments. Description is empty, limiting evidence, but the naming pattern matches other sibling assignment tools (assign_issue_to_user, assign_task_to_user, assign_user_story_to_user)…
Documented attack patterns abuse exactly the kind of access assign_epic_to_user 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 assign_epic_to_user:
{
"version": "1",
"default": "deny",
"tools": {
"assign_epic_to_user": {
"limits": [
{
"counter": "assign_epic_to_user_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}assign_epic_to_user 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.
Free to start. No card required.
assign_epic_to_user. It is categorised as a Write tool in the Taiga MCP Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Taiga MCP Bridge MCP server in PolicyLayer and add a rule for assign_epic_to_user: 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.
assign_epic_to_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the assign_epic_to_user 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.
Set action: deny in the PolicyLayer policy for assign_epic_to_user. 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.
assign_epic_to_user 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.
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.