AI agents call search_wiki to retrieve information from Wikimcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data from the wiki without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—worst case is unauthorized information disclosure from an existing wiki, but no data can be altered or destroyed. It belongs unambiguously in the Read category.
From the tool's definition Full-text search across all wiki pages is a query operation with no data modification. The tool description uses 'search', a canonical Read verb, and the server context shows sibling tools like 'read_page', 'list_pages', 'get_related', and 'get_subgraph'…
Attacks that exploit this kind of access
Full-text search across all wiki pages. It is categorised as a Read tool in the Wikimcp MCP Server, which means it retrieves data without modifying state.
Register the Wiki MCP server in PolicyLayer and add a rule for search_wiki: 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 Wikimcp. Nothing to install.
search_wiki 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 search_wiki 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 search_wiki. 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.
search_wiki is provided by the Wiki MCP server (mohith-das/wikimcp). 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 →