remove_label · Tickr MCP: Risk & Policy

WHAT IT DOES

What remove_label does on Tickr

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

PARAMETERS

Parameter	Type	Required	Description
`number`	string	Yes	Ticket display number, e.g. 'TKR-42' (legacy) or 'TKR-BUG-0042' (typed)
`label_id`	string	Yes	UUID of the label to remove

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why remove_label needs a policy

Removing a label modifies ticket metadata but is generally reversible (the label can be re-added), making this a Write operation. Misuse could cause organizational/categorization issues but no irreversible data loss.

From the tool's definition 'Remove a label from a ticket' — removes metadata (a label) from a ticket

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_label Rate-limited

remove_label 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": {
    "remove_label": {
      "limits": [
        {
          "counter": "remove_label_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 Tickr, so you can run agents against it safely.

FAQ

Questions about remove_label

What does the remove_label tool do? +

Remove a label from a ticket. It is categorised as a Write tool in the Tickr MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does remove_label accept? +

remove_label accepts 2 parameters: number, label_id. Required: number, label_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on remove_label? +

Register the Tickr MCP server in PolicyLayer and add a rule for remove_label: 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 Tickr. Nothing to install.

What risk level is remove_label? +

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

Can I rate-limit remove_label? +

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

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

remove_label is provided by the Tickr MCP server (@k-system/tickr-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.