This record as markdown: /tools/io-github-kivanccakmak-yaver/docs-search.md
What docs_search does on Yaver
AI agents call docs_search to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | Yes |
Parameters from the server's own tool schema.
Why docs_search is rated Low
docs_search performs a read-only search operation on documentation. It retrieves information based on a substring query but does not create, modify, delete, execute code, or affect any data or systems. This is a classic Read category tool with low severity since the blast radius of misuse is minimal: an agent could only retrieve existing documentation.
From the tool's definition 'Substring search across all doc pages' — a query-only operation that retrieves documentation without modification or side effects.
Attacks that exploit this kind of access
The rule that runs docs_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For docs_search, this is the rule to start with:
docs_search 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 Yaver, apply this rule, and every docs_search call is checked against it from then on.
Questions about docs_search
Substring search across all doc pages. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
docs_search accepts 1 parameter: q. Required: q. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for docs_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 Yaver. Nothing to install.
docs_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 docs_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 docs_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.
docs_search is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue