Alias of yuque_update_repository_toc for compatibility with official naming.
AI agents use yuque_update_toc to create or update resources in Yuque Mcp Plus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yuque Mcp Plus environment.
Updating a table of contents modifies the organizational structure of knowledge base content. This is reversible (can be undone by updating again) and does not irreversibly delete data, so it is Write rather than Destructive. The blast radius is medium because misuse could corrupt document hierarchies or organizational structures, but the effects are recoverable.
From the tool's definition Tool name 'yuque_update_toc' and description indicating it updates repository table of contents (ToC) structure.
Attacks that exploit this kind of access
Alias of yuque_update_repository_toc for compatibility with official naming. It is categorised as a Write tool in the Yuque Mcp Plus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Yuque Mcp Plus MCP server in PolicyLayer and add a rule for yuque_update_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 Plus. Nothing to install.
yuque_update_toc 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 yuque_update_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 yuque_update_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.
yuque_update_toc 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 →