AI agents call get_organization_group_overview 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 |
|---|---|---|---|
groupId | string | Yes | Group ID. Use list_organization_groups to discover valid group IDs. |
memberLimit | number | — | Maximum members to include in the overview. Defaults to 5. Set to 0 to exclude. |
includeMembers | boolean | — | Whether to include group members. Defaults to true. |
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 queries organizational data without any side effects, creation, modification, or deletion. The explicit 'read-only' designation confirms it is a pure data retrieval operation with no ability to alter state.
From the tool's definition Tool description explicitly states 'read-only call' and performs retrieval of 'comprehensive overview of a Yunxiao organization group including basic info and members' with no modification capabilities.
Attacks that exploit this kind of access
Get a comprehensive overview of a Yunxiao organization group including basic info and members in one read-only call. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_organization_group_overview accepts 4 parameters: groupId, memberLimit, includeMembers, organizationId. Required: groupId. 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_organization_group_overview: 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_organization_group_overview 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_organization_group_overview 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_organization_group_overview. 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_organization_group_overview 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 →