Move a Linear issue to another workflow status
AI agents use update_issue_status to create or update resources in MCPX MCP Gateway — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCPX MCP Gateway environment.
This tool creates or modifies data in a reversible manner (changing an issue's workflow status), which fits the Write category. It is not Destructive because the change is reversible (status can be moved again). Severity is medium because misuse could disrupt workflow tracking and project management, but the blast radius is limited to a single issue's metadata state, not data loss or financial impact.
From the tool's definition Tool description states 'Move a Linear issue to another workflow status' — this modifies the status field of an existing issue, which is a reversible state change to data.
Documented attack patterns abuse exactly the kind of access update_issue_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCPX MCP Gateway, and nothing reaches the server without passing your rules. This is the rule we recommend for update_issue_status:
{
"version": "1",
"default": "deny",
"tools": {
"update_issue_status": {
"limits": [
{
"counter": "update_issue_status_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_issue_status 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.
Move a Linear issue to another workflow status. It is categorised as a Write tool in the MCPX MCP Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCPX MCP Gateway MCP server in PolicyLayer and add a rule for update_issue_status: 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 MCPX MCP Gateway. Nothing to install.
update_issue_status 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 update_issue_status 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 update_issue_status. 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.
update_issue_status is provided by the MCPX MCP Gateway MCP server (thelunarcompany/lunar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 MCPX MCP Gateway tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 MCPX MCP Gateway tools catalogued and risk-classified — across an index of 42,500+ MCP servers.