ticket_batch_create · Trac MCP: Risk & Policy

WHAT IT DOES

What ticket_batch_create does on Trac

AI agents use ticket_batch_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_batch_create needs a policy

The tool creates tickets (data records) but does not delete or irreversibly destroy them. While batch operations create multiple records and could affect many items, the effects are reversible through deletion or modification. This is a Write operation rather than Destructive. Severity is medium because batch creation affects multiple records but is not destructive or financial in nature.

From the tool's definition Tool description states 'Create multiple tickets in a single batch operation.' The verb 'create' and the context of ticket creation indicate data creation, which is a write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ticket_batch_create Rate-limited

ticket_batch_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_batch_create": {
      "limits": [
        {
          "counter": "ticket_batch_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_batch_create

What does the ticket_batch_create tool do? +

Create multiple tickets in a single batch operation. Best-effort: all items attempted, per-item results reported. Bounded by TRAC_MAX_PARALLEL_REQUESTS semaphore. 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_batch_create? +

Register the Trac MCP server in PolicyLayer and add a rule for ticket_batch_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_batch_create? +

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

Can I rate-limit ticket_batch_create? +

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

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

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