Generic Yuque OpenAPI request passthrough for endpoints not wrapped by dedicated tools.
AI agents invoke yuque_request to trigger actions in Yuque Mcp Plus. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This is a generic passthrough tool that can execute arbitrary Yuque OpenAPI requests. Since it is not constrained to any specific operation, it can perform any action the Yuque API supports — including reads, writes, deletions, and potentially financial operations.
From the tool's definition Generic Yuque OpenAPI request passthrough for endpoints not wrapped by dedicated tools.
Attacks that exploit this kind of access
Generic Yuque OpenAPI request passthrough for endpoints not wrapped by dedicated tools. It is categorised as a Execute tool in the Yuque Mcp Plus MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Yuque Mcp Plus MCP server in PolicyLayer and add a rule for yuque_request: 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_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the yuque_request 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_request. 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_request 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 →