This record as markdown: /tools/io-github-kivanccakmak-yaver/docs-list.md
What docs_list does on Yaver
AI agents call docs_list 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.
Why docs_list is rated Low
This tool queries and returns documentation metadata (a sidebar tree structure) without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal security impact—exposure of documentation structure poses no risk to system integrity, financial data, or operational safety.
From the tool's definition Tool name 'docs_list' and description 'Return the docs site sidebar tree' indicate retrieval of documentation structure with no modification or execution capabilities.
Attacks that exploit this kind of access
The rule that runs docs_list 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_list, this is the rule to start with:
docs_list 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_list call is checked against it from then on.
Questions about docs_list
Return the docs site sidebar tree. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for docs_list: 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_list 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_list 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_list. 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_list 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