Delete a doc by ID.
AI agents call yuque_delete_doc to permanently remove resources in Yuque Mcp Plus — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion operations are irreversible and cannot be undone. This falls squarely under the Destructive category as it permanently removes data. The high severity reflects that an AI agent misusing this tool could irretrievably delete important documentation, causing data loss across the knowledge base.
From the tool's definition Tool name 'yuque_delete_doc' with description 'Delete a doc by ID' explicitly performs irreversible deletion of documents.
Attacks that exploit this kind of access
Delete a doc by ID. It is categorised as a Destructive tool in the Yuque Mcp Plus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Yuque Mcp Plus MCP server in PolicyLayer and add a rule for yuque_delete_doc: 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_delete_doc is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the yuque_delete_doc 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_delete_doc. 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_delete_doc 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 →