linear_bulk_update_status

WHAT IT DOES

What linear_bulk_update_status does on Linear MCP Integration Server

AI agents use linear_bulk_update_status to create or update resources in Linear MCP Integration Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linear MCP Integration Server environment.

WHY IT NEEDS A POLICY

Why linear_bulk_update_status needs a policy

Bulk status updates modify issue data in Linear (reversible operation), affecting potentially many issues at once. This is Write category rather than Execute because it modifies data state rather than executing arbitrary code. Severity is high due to blast radius: a mistaken bulk update could change status on many issues, disrupting workflows, though changes are reversible.

From the tool's definition Tool name 'linear_bulk_update_status' indicates bulk modification of issue statuses. Server description mentions 'bulk updating statuses' as a capability. No detailed description provided for this specific tool.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

linear_bulk_update_status Rate-limited

linear_bulk_update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "linear_bulk_update_status": {
      "limits": [
        {
          "counter": "linear_bulk_update_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Linear MCP Integration Server, so you can run agents against it safely.

FAQ

Questions about linear_bulk_update_status

What does the linear_bulk_update_status tool do? +

linear_bulk_update_status. It is categorised as a Write tool in the Linear MCP Integration Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on linear_bulk_update_status? +

Register the Linear MCP Integration Server MCP server in PolicyLayer and add a rule for linear_bulk_update_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 Linear MCP Integration Server. Nothing to install.

What risk level is linear_bulk_update_status? +

linear_bulk_update_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit linear_bulk_update_status? +

Yes. Add a rate_limit block to the linear_bulk_update_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.

How do I block linear_bulk_update_status completely? +

Set action: deny in the PolicyLayer policy for linear_bulk_update_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.

What MCP server provides linear_bulk_update_status? +

linear_bulk_update_status is provided by the Linear MCP Integration Server MCP server (skspade/mcp-linear-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.