AI agents use linear_update_issue to create or update resources in Linear MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linear MCP Server environment.
This tool modifies data reversibly by updating issue properties (status, assignee, description, labels, etc.) without deleting or destroying records. It falls squarely in the Write category. Severity is medium because misuse could modify many issues or inject misleading information into the tracking system, affecting team workflow and decision-making, but changes can be reverted.
From the tool's definition Tool name 'linear_update_issue' and description 'Updates an existing Linear issue' indicate modification of existing data in Linear's issue tracking system.
Documented attack patterns abuse exactly the kind of access linear_update_issue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Linear MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for linear_update_issue:
{
"version": "1",
"default": "deny",
"tools": {
"linear_update_issue": {
"limits": [
{
"counter": "linear_update_issue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}linear_update_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.
Free to start. No card required.
Updates an existing Linear issue. It is categorised as a Write tool in the Linear MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Linear MCP Server MCP server in PolicyLayer and add a rule for linear_update_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 MCP Server. Nothing to install.
linear_update_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 linear_update_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 linear_update_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.
linear_update_issue is provided by the Linear MCP Server MCP server (jerhadf/linear-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Linear MCP Server, 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.
5 Linear MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.