Full-text search the bundled product documentation. Returns the best-matching pages as { path, title, url }, where url is the public HTTPS docs link you can cite. Use docs.get_page with a returned path to read a page.
AI agents call search_docs to retrieve information from Zion without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | |
query | string | Yes |
Parameters from the server's own tool schema.
This tool performs a read-only search operation that retrieves and indexes documentation without any side effects. It queries existing data (documentation pages) and returns structured results for citation, which is a classic Read operation. The severity is low because it only accesses documentation that is presumably public-facing and read-only.
From the tool's definition Tool description explicitly states 'Full-text search the bundled product documentation' and 'Returns the best-matching pages' with retrieval of metadata (path, title, url). No modification, deletion, or execution capabilities described.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Full-text search the bundled product documentation. Returns the best-matching pages as { path, title, url }, where url is the public HTTPS docs link you can cite. Use docs.get_page with a returned path to read a page. It is categorised as a Read tool in the Zion MCP Server, which means it retrieves data without modifying state.
search_docs accepts 2 parameters: limit, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Zion MCP server in PolicyLayer and add a rule for search_docs: 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 Zion. Nothing to install.
search_docs 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_docs 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_docs. 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_docs is provided by the Zion MCP server (zion-mcp). 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 →