ticket_create · Trac MCP: Risk & Policy

WHAT IT DOES

What ticket_create does on Trac

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

WHY IT NEEDS A POLICY

Why ticket_create needs a policy

The tool creates new records (tickets) in a Trac project management system. Creation of data is a Write operation—it modifies state reversibly (tickets can be deleted or edited later). While the server supports full CRUD operations, this specific tool only creates, not deletes or overwrites.

From the tool's definition Tool name: 'ticket_create'. Description: 'Create a new ticket.' This creates new data in the Trac system. The sibling tools include destructive operations (milestone_delete, ticket_batch_delete) and this tool is explicitly a creation operation, making it…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ticket_create Rate-limited

ticket_create 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_create": {
      "limits": [
        {
          "counter": "ticket_create_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 Trac, so you can run agents against it safely.

FAQ

Questions about ticket_create

What does the ticket_create tool do? +

Create a new ticket. Accepts Markdown for description (auto-converted to TracWiki). It is categorised as a Write tool in the Trac 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_create? +

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

What risk level is ticket_create? +

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

Can I rate-limit ticket_create? +

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

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

ticket_create is provided by the Trac MCP server (nerpatech/trac-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.