Create a repository.
AI agents use yuque_create_repo 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.
Creating a repository is a write operation that adds new data structures to the knowledge base. While it has blast radius in terms of cluttering the workspace or consuming quota, it is reversible (the sibling tool 'yuque_delete_repo' confirms deletability) and does not move money, execute arbitrary code, or permanently destroy data.
From the tool's definition Tool name 'yuque_create_repo' and description 'Create a repository' indicate creation of a new resource in the Yuque platform. This is a reversible data creation operation (repositories can be deleted).
Attacks that exploit this kind of access
Create a repository. 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_create_repo: 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_create_repo 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_create_repo 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_create_repo. 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_create_repo 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 →