This record as markdown: /tools/0thomas1-kanban-mcp/move-task.md
What move-task does on Kanban MCP Server
AI agents use move-task to create or update resources in Kanban MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kanban MCP Server environment.
Why move-task is rated Medium
This tool changes task metadata (status field) but does not delete, execute code, trigger financial transactions, or cause irreversible damage. The modification is reversible—tasks can be moved back to previous statuses. This is a classic Write operation: data modification without permanent loss.
From the tool's definition Tool description states 'move a task to a different status', which modifies task state reversibly without deleting data or executing external operations.
Attacks that exploit this kind of access
The rule that runs move-task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kanban MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move-task, this is the rule to start with:
move-task 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Kanban MCP Server, apply this rule, and every move-task call is checked against it from then on.
Questions about move-task
move a task to a different status. It is categorised as a Write tool in the Kanban MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kanban MCP Server MCP server in PolicyLayer and add a rule for move-task: 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 MCP Server. Nothing to install.
move-task 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 move-task 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 move-task. 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.
move-task is provided by the Kanban MCP Server MCP server (0thomas1/kanban-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Kanban MCP Server, and thousands of servers like it.
This server
Across the catalogue