remove_release_ticket · Tickr MCP: Risk & Policy

WHAT IT DOES

What remove_release_ticket does on Tickr

AI agents use remove_release_ticket 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
`project`	string	Yes	Project slug
`ticket_id`	string	Yes	UUID of the ticket to remove from the release
`release_id`	string	Yes	UUID of the release

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why remove_release_ticket needs a policy

Removing a ticket from a release is a reversible association change (the ticket and release both continue to exist); it can be undone by re-adding the ticket. This is a Write-level modification rather than Destructive, though misuse could disrupt release planning. Severity is medium due to potential release management impact.

From the tool's definition 'Remove a ticket from a release' — dissociates a ticket from a release without necessarily deleting either artifact

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_release_ticket Rate-limited

remove_release_ticket 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_release_ticket": {
      "limits": [
        {
          "counter": "remove_release_ticket_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_release_ticket

What does the remove_release_ticket tool do? +

Remove a ticket from a release. 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_release_ticket accept? +

remove_release_ticket accepts 3 parameters: project, ticket_id, release_id. Required: project, ticket_id, release_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on remove_release_ticket? +

Register the Tickr MCP server in PolicyLayer and add a rule for remove_release_ticket: 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_release_ticket? +

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

Can I rate-limit remove_release_ticket? +

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

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

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