search_wiki
Full-text search across all wiki page content.
This record as markdown: /tools/agent-store/search-wiki.md
What search_wiki does on Agent Store
AI agents call search_wiki to retrieve information from Agent Store without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_wiki is rated Low
search_wiki is a search/query function that reads wiki content for informational purposes. It has no capability to modify, delete, or execute code. The blast radius is minimal: at worst, an agent might retrieve sensitive information if wiki access controls are insufficient, but the tool itself only reads data. Classified as Read with low severity.
From the tool's definition Tool performs 'full-text search across all wiki page content' — a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs search_wiki safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agent Store, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_wiki, this is the rule to start with:
search_wiki is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Agent Store, apply this rule, and every search_wiki call is checked against it from then on.
Questions about search_wiki
Full-text search across all wiki page content. It is categorised as a Read tool in the Agent Store MCP Server, which means it retrieves data without modifying state.
Register the Agent Store 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 Agent Store. 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 Agent Store MCP server (chrisluersen/agent-store). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agent Store, and thousands of servers like it.
This server
Across the catalogue