AI agents use add_relationship to create or update resources in Kanban — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kanban environment.
The tool creates a new relationship record (reversible write operation) between existing kanban items. This modifies the board's structure by adding metadata but does not delete data or execute arbitrary code. Given the sibling tools include destructive operations (delete_item, delete_decision, delete_tag) and the tool name clearly indicates creation/addition, this is a Write-category operation.
From the tool's definition Tool name 'add_relationship' indicates creating a new relationship link between kanban board items. The context of a kanban-mcp server with 40+ tools for tracking issues, features, todos, and epics suggests this creates associations or dependencies between…
Documented attack patterns abuse exactly the kind of access add_relationship gives an agent:
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 add_relationship:
{
"version": "1",
"default": "deny",
"tools": {
"add_relationship": {
"limits": [
{
"counter": "add_relationship_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_relationship 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.
add_relationship. It is categorised as a Write tool in the Kanban MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kanban MCP server in PolicyLayer and add a rule for add_relationship: 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.
add_relationship 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 add_relationship 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 add_relationship. 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.
add_relationship 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.
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.