AI agents call wiki_search 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 performs a read-only query operation against wiki pages. It retrieves and ranks existing content but does not create, modify, delete, or execute any operations. Misuse would result in information disclosure at worst, with minimal blast radius since wiki pages are typically readable by authorized users anyway.
From the tool's definition Tool name is 'wiki_search' and description states it 'Search wiki pages by content' and 'Returns snippets showing matched text.' The verb 'search' combined with 'returns' indicates data retrieval with no modification, creation, or deletion.
Attacks that exploit this kind of access
Search wiki pages by content with relevance ranking. Returns snippets showing matched text. Set raw=true to get snippets in original TracWiki format without conversion. 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_search: 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_search 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_search 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_search. 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_search 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 →