ticket-write · MCP Backlog Server MCP: Risk & Policy

WHAT IT DOES

What ticket-write does on MCP Backlog Server

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

WHY IT NEEDS A POLICY

Why ticket-write needs a policy

This tool creates and modifies work items reversibly. It does not delete data (that would be Destructive, handled by 'prune' or 'done'), does not execute arbitrary code (would be Execute), and does not move money (would be Financial).

From the tool's definition Tool name 'ticket-write' and description 'Write access to backlog tickets - create and update tickets for backlog items' explicitly indicate create and update operations on backlog data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ticket-write Rate-limited

ticket-write 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": {
    "ticket-write": {
      "limits": [
        {
          "counter": "ticket-write_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 MCP Backlog Server, so you can run agents against it safely.

FAQ

Questions about ticket-write

What does the ticket-write tool do? +

Write access to backlog tickets - create and update tickets for backlog items. It is categorised as a Write tool in the MCP Backlog 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 ticket-write? +

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

What risk level is ticket-write? +

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

Can I rate-limit ticket-write? +

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

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

ticket-write is provided by the MCP Backlog Server MCP server (rwese/mcp-backlog). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.