AI agents call wiki_recent_changes to retrieve information from Trac without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical metadata about wiki pages without creating, modifying, or deleting any data. It is a passive query operation that has no impact on the Trac project state. Even though the server enables destructive operations (milestone_delete, ticket_batch_delete), this specific tool is purely informational and poses minimal risk if misused by an AI agent.
From the tool's definition Tool description states 'Get recently modified wiki pages' and 'Returns pages sorted by modification date'. The verb 'get' and 'returns' indicate read-only retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get recently modified wiki pages. Returns pages sorted by modification date (newest first). Useful for finding stale or recently updated documentation. It is categorised as a Read tool in the Trac MCP Server, which means it retrieves data without modifying state.
Register the Trac MCP server in PolicyLayer and add a rule for wiki_recent_changes: 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_recent_changes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the wiki_recent_changes 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_recent_changes. 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_recent_changes 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 →