Alias of yuque_get_docs for compatibility with official naming.
AI agents call yuque_list_docs to retrieve information from Yuque Mcp Plus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a list of documents from the Yuque knowledge base. It performs a read-only query operation with no side effects, no data modification, and no irreversible actions. The blast radius of misuse is minimal—an AI agent could only retrieve document information it may not be authorized to view, which is a low-severity information disclosure risk.
From the tool's definition Tool is an alias for yuque_get_docs, which retrieves/lists documents. The description indicates it 'lists documents' without modifying, creating, or deleting data.
Attacks that exploit this kind of access
Alias of yuque_get_docs for compatibility with official naming. It is categorised as a Read tool in the Yuque Mcp Plus MCP Server, which means it retrieves data without modifying state.
Register the Yuque Mcp Plus MCP server in PolicyLayer and add a rule for yuque_list_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 Yuque Mcp Plus. Nothing to install.
yuque_list_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 yuque_list_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 yuque_list_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.
yuque_list_docs is provided by the Yuque Mcp Plus MCP server (michealjou/yuque-mcp-plus). 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 →