Get repository statistics for a group.
AI agents call yuque_group_book_stats 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 retrieves statistical information about repositories within a group. It performs no data modification, deletion, or execution of arbitrary operations. The blast radius of misuse is minimal—at worst, an agent could access aggregate statistics it shouldn't see, but cannot alter data or trigger external actions. This is a straightforward Read operation.
From the tool's definition Tool name 'yuque_group_book_stats' and description 'Get repository statistics for a group' indicate a retrieval operation. The verb 'Get' and the nature of 'statistics' (aggregated, read-only data) confirm this is a query with no side effects.
Attacks that exploit this kind of access
Get repository statistics for a group. 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_group_book_stats: 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_group_book_stats 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_group_book_stats 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_group_book_stats. 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_group_book_stats 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 →