AI agents use wiki_file_push 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.
This tool modifies wiki pages by creating new ones or updating existing ones. These are reversible write operations—the content can be edited, reverted, or replaced later. It does not delete data (which would be Destructive), execute arbitrary code (which would be Execute), or move money (Financial).
From the tool's definition Tool description states it 'creates or updates the wiki page', which are reversible write operations. The phrase 'Push a local file to a Trac wiki page' indicates data modification without deletion.
Attacks that exploit this kind of access
Push a local file to a Trac wiki page. Reads the file, auto-detects format (Markdown/TracWiki), converts if needed, and creates or updates the wiki page. 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.
Register the Trac MCP server in PolicyLayer and add a rule for wiki_file_push: 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.
wiki_file_push is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the wiki_file_push 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.
Set action: deny in the PolicyLayer policy for wiki_file_push. 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.
wiki_file_push 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →