AI agents call get_department_usage to retrieve information from Yunxiao without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | number | — | Page number for pagination. Starts at 1. |
endTime | string | Yes | End time for the usage query range (inclusive). Format: yyyy-MM-ddTHH:mm:ss+08:00. |
perPage | number | — | Page size for pagination. Supports 1-100. Defaults to 100 when omitted. |
startTime | string | Yes | Start time for the usage query range (inclusive). Format: yyyy-MM-ddTHH:mm:ss+08:00 (e.g. 2024-01-01T00:00:00+08:00). |
departmentId | string | Yes | Department ID. Use list_organization_departments to discover valid department IDs. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
Parameters from the server's own tool schema.
This tool queries and retrieves usage metrics for analytical purposes. It performs no write operations, does not execute arbitrary code, does not delete data, and does not involve financial transactions. The action is purely informational retrieval with no side effects on the system.
From the tool's definition Tool name 'get_department_usage' and description 'Get Tongyi Lingma usage metrics for a specific department over a time range' indicates retrieval of existing metrics data without modification or deletion.
Attacks that exploit this kind of access
Get Tongyi Lingma usage metrics for a specific department over a time range. Use this to analyze AI coding assistant adoption within a department. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_department_usage accepts 6 parameters: page, endTime, perPage, startTime, departmentId, organizationId. Required: endTime, startTime, departmentId. The full parameter table on this page comes from the server's own tool schema.
Register the Yunxiao MCP server in PolicyLayer and add a rule for get_department_usage: 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 Yunxiao. Nothing to install.
get_department_usage 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 get_department_usage 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 get_department_usage. 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.
get_department_usage is provided by the Yunxiao MCP server (@futuretea/yunxiao-mcp-server). 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 →