move_issue
Move an issue to a different workflow state (kanban column) by state name or ID
This record as markdown: /tools/0xikarus-linear-kanban-mcp/move-issue.md
What move_issue does on Linear Kanban Server
AI agents use move_issue to create or update resources in Linear Kanban Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linear Kanban Server environment.
Why move_issue is rated Medium
This tool creates or modifies data reversibly by transitioning an issue between workflow states. It does not delete or irreversibly destroy data (excluding Destructive category), does not execute arbitrary code or external operations (excluding Execute), and does not involve financial transactions (excluding Financial).
From the tool's definition Tool description states it 'Move[s] an issue to a different workflow state' which modifies the state of an issue within Linear.
Attacks that exploit this kind of access
The rule that runs move_issue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linear Kanban Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_issue, this is the rule to start with:
move_issue 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 Linear Kanban Server, apply this rule, and every move_issue call is checked against it from then on.
Questions about move_issue
Move an issue to a different workflow state (kanban column) by state name or ID. It is categorised as a Write tool in the Linear Kanban Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Linear Kanban Server MCP server in PolicyLayer and add a rule for move_issue: 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 Linear Kanban Server. Nothing to install.
move_issue 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_issue 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_issue. 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_issue is provided by the Linear Kanban Server MCP server (0xikarus/linear-kanban-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linear Kanban Server, and thousands of servers like it.
This server
Across the catalogue