publish_release · Tickr MCP: Risk & Policy

WHAT IT DOES

What publish_release does on Tickr

AI agents use publish_release 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
`release_id`	string	Yes	UUID of the release to publish

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why publish_release needs a policy

This tool creates or modifies data reversibly. Publishing a release changes its status and records metadata (publishedAt), which are state changes. However, these modifications are reversible (the release can be unpublished or the status changed back), so this does not qualify as Destructive. It is not Execute (no code/command execution), Financial, or Read. Write is the appropriate category.

From the tool's definition Tool name and description: 'publish_release' — 'sets status to published and records publishedAt timestamp'. This modifies release state and adds a timestamp record.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

publish_release Rate-limited

publish_release 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": {
    "publish_release": {
      "limits": [
        {
          "counter": "publish_release_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 publish_release

What does the publish_release tool do? +

Publish a draft release — sets status to published and records publishedAt timestamp. 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 publish_release accept? +

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

How do I enforce a policy on publish_release? +

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

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

Can I rate-limit publish_release? +

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

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

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