Get the table of contents (directory structure) of the Yuque knowledge base. Use this when user wants to browse or navigate the folder structure. Returns a flat list of all folders and documents with uuid and title.
AI agents call get_toc to retrieve information from Yuque MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a purely read-only operation that queries the knowledge base structure without any side effects. It retrieves existing data for navigation purposes, fitting the Read category. The blast radius is minimal—malicious use would only expose organizational structure of documents already accessible to the authenticated user.
From the tool's definition Tool retrieves and returns directory structure and metadata (uuid, title) of knowledge base folders and documents. No modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get the table of contents (directory structure) of the Yuque knowledge base. Use this when user wants to browse or navigate the folder structure. Returns a flat list of all folders and documents with uuid and title. It is categorised as a Read tool in the Yuque MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Yuque MCP Server MCP server in PolicyLayer and add a rule for get_toc: 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 Yuque MCP Server. Nothing to install.
get_toc 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 get_toc 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 get_toc. 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.
get_toc is provided by the Yuque MCP Server MCP server (wangx-wx/yuque-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 →