wiki_update · Trac MCP: Risk & Policy

WHAT IT DOES

What wiki_update does on Trac

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

This tool creates or modifies data reversibly (updates wiki pages). Users can revert changes via version control. It does not delete or destroy data (Destructive), execute arbitrary code (Execute), or move money (Financial).

From the tool's definition 'Update existing wiki page' explicitly modifies data; 'optimistic locking' and 'version for conflict detection' indicate reversible updates that preserve history.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wiki_update Rate-limited

wiki_update 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": {
    "wiki_update": {
      "limits": [
        {
          "counter": "wiki_update_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 wiki_update

What does the wiki_update tool do? +

Update existing wiki page with optimistic locking. Requires version for conflict detection. 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 wiki_update? +

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

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

Can I rate-limit wiki_update? +

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

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

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