AI agents use edit_item 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 modifies data reversibly (editing items in the kanban board) without deleting or executing arbitrary code. While the empty description reduces confidence slightly, the tool name and server context clearly indicate a Write operation. Severity is medium because editing kanban items could affect workflow visibility and task tracking, but the impact is limited to individual items and reversible.
From the tool's definition Tool name 'edit_item' indicates modification of existing data in a kanban board system. Description is empty, but within the context of a database-backed kanban server with 40+ tools for tracking issues, features, todos, and epics, 'edit' typically means…
Documented attack patterns abuse exactly the kind of access edit_item 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 edit_item:
{
"version": "1",
"default": "deny",
"tools": {
"edit_item": {
"limits": [
{
"counter": "edit_item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}edit_item 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.
edit_item. 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 edit_item: 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.
edit_item 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 edit_item 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 edit_item. 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.
edit_item 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.