milestone_create · Trac MCP: Risk & Policy

WHAT IT DOES

What milestone_create does on Trac

AI agents use milestone_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 milestone_create needs a policy

Creating a new milestone is a reversible write operation that adds data to the project management system. It does not execute arbitrary code, delete data, or move money. The 'medium' severity reflects that misconfiguration could clutter the project with unwanted milestones, but this is recoverable via deletion. The tool requires TICKET_ADMIN permission, limiting but not eliminating misuse risk.

From the tool's definition Tool name 'milestone_create' and description state it 'Create a new milestone' with attributes for due date, completed date, and description. This creates new data in the Trac system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

milestone_create Rate-limited

milestone_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": {
    "milestone_create": {
      "limits": [
        {
          "counter": "milestone_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 milestone_create

What does the milestone_create tool do? +

Create a new milestone. Requires TICKET_ADMIN permission. Attributes: due (ISO 8601 date), completed (ISO 8601 date or 0), description (string). 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 milestone_create? +

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

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

Can I rate-limit milestone_create? +

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

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

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