AI agents call list_organization_departments 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. |
perPage | number | — | Page size for pagination. Supports 1-100. |
parentId | string | — | Parent department ID. Use list_organization_departments with an empty parentId to discover top-level departments, then drill down by setting this to a discovere |
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 retrieves and enumerates departmental information from the organization. It performs no modifications, deletions, or external operations. The primary use case is data discovery to support filtering and organization—a read-only operation. The low severity reflects minimal blast radius; misuse would expose organizational structure but not enable destructive, financial, or system-compromising actions.
From the tool's definition Tool name 'list_organization_departments' and description 'List departments in a Yunxiao organization' indicate a query operation that retrieves organizational structure data.
Attacks that exploit this kind of access
List departments in a Yunxiao organization. Use this to discover department IDs for filtering members or assigning work items. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_organization_departments accepts 4 parameters: page, perPage, parentId, organizationId. 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 list_organization_departments: 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.
list_organization_departments 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 list_organization_departments 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 list_organization_departments. 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.
list_organization_departments 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 →