Update an existing document in Yuque knowledge base. Modify title, content, path, or visibility.
AI agents use update_doc to create or update resources in Yuque MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yuque MCP Server environment.
The tool modifies existing documents in a Yuque knowledge base but does not delete or destroy data (which would be Destructive), nor does it move money (Financial) or execute arbitrary code (Execute). Updates are reversible through subsequent edits or version control.
From the tool's definition Tool description explicitly states 'Update an existing document' and allows modification of 'title, content, path, or visibility' — classic write operations that create or modify data reversibly.
Attacks that exploit this kind of access
Update an existing document in Yuque knowledge base. Modify title, content, path, or visibility. It is categorised as a Write tool in the Yuque MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Yuque MCP Server MCP server in PolicyLayer and add a rule for update_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 Server. Nothing to install.
update_doc is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_doc 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 →