get_group_member_list
AI agents call get_group_member_list to retrieve information from Xadeus-QQ-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves a list of group members—a read-only query operation with no side effects. Even if misused by an agent, it only exposes existing group membership data already accessible through normal QQ group interfaces. Confidence is slightly lower due to empty description, but naming convention and context from sibling tools provide strong signal that this is a basic data retrieval function.
From the tool's definition Tool name 'get_group_member_list' follows Read-category naming pattern (get_*). Sibling tools include 'get_friend_list', 'get_group_list', and 'batch_get_recent_context', all consistent with data retrieval operations.
Attacks that exploit this kind of access
get_group_member_list. It is categorised as a Read tool in the Xadeus-QQ-MCP MCP Server, which means it retrieves data without modifying state.
Register the Xadeus-QQ- MCP server in PolicyLayer and add a rule for get_group_member_list: 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 Xadeus-QQ-MCP. Nothing to install.
get_group_member_list 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_group_member_list 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_group_member_list. 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_group_member_list is provided by the Xadeus-QQ- MCP server (mouse114514/xadeus-qq-mcp). 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 →