This record as markdown: /tools/linear/linear-transferissue.md
What linear_transferIssue does on Linear
AI agents use linear_transferIssue to create or update resources in Linear, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linear environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
teamId | string | — | ID of the team to transfer the issue to |
issueId | string | — | ID or identifier of the issue to transfer (e.g., ABC-123) |
Parameters from the server's own tool schema.
Why linear_transferIssue is rated Medium
Transferring an issue to another team modifies the issue's team assignment. This is a reversible write operation (the issue can be transferred back), not destructive. Misuse could disrupt team workflows by moving issues to wrong teams.
From the tool's definition Transfer an issue to another team
Attacks that exploit this kind of access
The rule that runs linear_transferIssue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linear, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linear_transferIssue, this is the rule to start with:
linear_transferIssue 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, apply this rule, and every linear_transferIssue call is checked against it from then on.
Questions about linear_transferIssue
Transfer an issue to another team. It is categorised as a Write tool in the Linear MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
linear_transferIssue accepts 2 parameters: teamId, issueId. The full parameter table on this page comes from the server's own tool schema.
Register the Linear MCP server in PolicyLayer and add a rule for linear_transferIssue: 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. Nothing to install.
linear_transferIssue 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 linear_transferIssue 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 linear_transferIssue. 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.
linear_transferIssue is provided by the Linear MCP server (@linear-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linear, and thousands of servers like it.
This server
Across the catalogue