Delete a wiki page. Warning: This cannot be undone. Requires WIKI_DELETE permission.
AI agents call wiki_delete to permanently remove resources in Trac — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a wiki page is an irreversible destructive operation that permanently removes data. The warning in the description reinforces this is not a reversible write operation. High severity because wiki pages may contain important project documentation, and an AI agent with misused access could delete critical information affecting the entire project team.
From the tool's definition Tool description explicitly states 'Delete a wiki page' and 'Warning: This cannot be undone.' The name 'wiki_delete' confirms deletion intent.
Attacks that exploit this kind of access
Delete a wiki page. Warning: This cannot be undone. Requires WIKI_DELETE permission. It is categorised as a Destructive tool in the Trac MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Trac MCP server in PolicyLayer and add a rule for wiki_delete: 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_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the wiki_delete 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_delete. 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_delete 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 →