Get the current Yuque user.
AI agents call yuque_get_user to retrieve information from Yuque Mcp Plus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns information about the current authenticated user. It performs a read-only operation with no ability to modify, delete, or execute actions. The blast radius if misused is minimal — an AI agent could learn user identity information but cannot cause harm to data or systems. Classified as Read with low severity.
From the tool's definition Tool name is 'yuque_get_user' and description states 'Get the current Yuque user' — retrieves user information with no modification or side effects.
Attacks that exploit this kind of access
Get the current Yuque user. It is categorised as a Read tool in the Yuque Mcp Plus MCP Server, which means it retrieves data without modifying state.
Register the Yuque Mcp Plus MCP server in PolicyLayer and add a rule for yuque_get_user: 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_get_user is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the yuque_get_user 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_get_user. 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_get_user 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 →