Medium Risk

linear_addIssueLabel

Add a label to an issue in Linear

Part of the Linear server.

linear_addIssueLabel can modify Linear data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE LINEAR →

Free to start. No card required.

AI agents use linear_addIssueLabel to create or modify resources in Linear. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call linear_addIssueLabel repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Linear.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "linear_addIssueLabel": {
      "limits": [
        {
          "counter": "linear_addissuelabel_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Linear policy for all 66 tools.

Get this rule live on your own Linear server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY LINEAR →

View all 66 tools →

These attack patterns abuse exactly the kind of access linear_addIssueLabel gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so linear_addIssueLabel only ever does what you allow.

SECURE LINEAR →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the linear_addIssueLabel tool do? +

Add a label to an issue in Linear. 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.

How do I enforce a policy on linear_addIssueLabel? +

Register the Linear MCP server in PolicyLayer and add a rule for linear_addIssueLabel: 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.

What risk level is linear_addIssueLabel? +

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

Can I rate-limit linear_addIssueLabel? +

Yes. Add a rate_limit block to the linear_addIssueLabel 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_addIssueLabel completely? +

Set action: deny in the PolicyLayer policy for linear_addIssueLabel. 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_addIssueLabel? +

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

Enforce policy on every Linear tool call.

Deterministic rules across all 66 Linear tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.