// SCAN REPORT

Trac

27 tools. 13 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated: 30 Jun 2026

13 can modify or destroy data

14 read-only

27 tools total

Community server · catalogue entry verified 30/06/2026

How to control Trac ↓

TOOL MAP

What Trac exposes to your agents

Read (14) Write / Execute (9) Destructive / Financial (4)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Trac tools

Destructive · High milestone_delete This tool permanently deletes milestones, which is an irreversible operation that destroys data. Destructive · High ticket_batch_delete Deletion is a destructive operation that cannot be undone. Destructive · High ticket_delete This tool irreversibly deletes data (tickets) from the Trac project management system. Destructive · High wiki_delete Deleting a wiki page is an irreversible destructive operation that permanently removes data.

13 of Trac's 27 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Trac

PolicyLayer is an MCP gateway — it sits between your AI agents and Trac, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "milestone_delete": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "milestone_create": {
    "limits": [
      {
        "counter": "milestone_create_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_server_time": {
    "limits": [
      {
        "counter": "get_server_time_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Trac — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON TRAC →

Instant setup, no code required.

FULL CATALOGUE

All 27 Trac tools

DESTRUCTIVE 4 tools

Destructive milestone_delete Delete a milestone by name. Requires TICKET_ADMIN permission. Warning: This cannot be undone. Destructive ticket_batch_delete Delete multiple tickets in a single batch operation. Best-effort: all items attempted, per-item results report Destructive ticket_delete Delete a ticket permanently. Warning: This cannot be undone. Requires TICKET_ADMIN permission and Destructive wiki_delete Delete a wiki page. Warning: This cannot be undone. Requires WIKI_DELETE permission.

WRITE 9 tools

Write milestone_create Create a new milestone. Requires TICKET_ADMIN permission. Attributes: due (ISO 8601 date), completed (ISO 8601 Write milestone_update Update an existing milestone. Requires TICKET_ADMIN permission. Attributes: due (ISO 8601 date), completed (IS Write ticket_batch_create Create multiple tickets in a single batch operation. Best-effort: all items attempted, per-item results report Write ticket_batch_update Update multiple tickets in a single batch operation. Best-effort: all items attempted, per-item results report Write ticket_create Create a new ticket. Accepts Markdown for description (auto-converted to TracWiki). Write ticket_update Update ticket attributes and/or add comments. Uses optimistic locking to prevent conflicts. Accepts Markdown f Write wiki_create Create new wiki page from Markdown input. Fails if page exists (use wiki_update instead). Write wiki_file_push Push a local file to a Trac wiki page. Reads the file, auto-detects format (Markdown/TracWiki), converts if ne Write wiki_update Update existing wiki page with optimistic locking. Requires version for conflict detection.

READ 14 tools

Read get_server_time Get current Trac server time for temporal reasoning and coordination. Returns server timestamp in both ISO 860 Read milestone_get Get milestone details by name. Returns name, due date, completion date, and description. Requires TICKET_VIEW Read milestone_list List all milestone names. Returns array of milestone names (e.g., [ Read ping Test Trac MCP server connectivity and return API version Read ticket_actions Get valid workflow actions for a ticket Read ticket_changelog Get ticket change history. Use this to investigate who changed what and when. Set raw=true to get comment cont Read ticket_fields Get all ticket field definitions (standard + custom fields). Returns field metadata including name, type, labe Read ticket_get Get full ticket details including summary, description, status, and owner. Use ticket_changelog for history. S Read ticket_search Search tickets with filtering by status, owner, and keywords. Returns ticket IDs with summaries. Read wiki_file_detect_format Detect the format of a local file (Markdown or TracWiki). Uses file extension first, then content-based heuris Read wiki_file_pull Pull a Trac wiki page to a local file. Fetches page content, converts to the requested format, and writes to t Read wiki_get Get wiki page content with Markdown output. Returns full content with metadata (version, author, modified date Read wiki_recent_changes Get recently modified wiki pages. Returns pages sorted by modification date (newest first). Useful for finding Read wiki_search Search wiki pages by content with relevance ranking. Returns snippets showing matched text. Set raw=true to ge

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Trac

Can an AI agent delete data through the Trac MCP server? +

Yes. The Trac server exposes 4 destructive tools including milestone_delete, ticket_batch_delete, ticket_delete. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Trac? +

The Trac server has 9 write tools including milestone_create, milestone_update, ticket_batch_create. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Trac.

How many tools does the Trac MCP server expose? +

27 tools across 3 categories: Destructive, Read, Write. 14 are read-only. 13 can modify, create, or delete data.

How do I enforce a policy on Trac? +

Register the Trac MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Trac tool call.

Deterministic rules across all 27 Trac tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON TRAC →

Instant setup, no code required.

27 Trac tools catalogued and risk-classified — across an index of 43,000+ MCP servers.