Retrieves the complete member list of an existing group chat in RongCloud.
AI agents call get_group_members to retrieve information from RongCloud MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries existing group membership data and returns it without creating, modifying, deleting, or executing any operations. It is a standard read/fetch operation with minimal risk even if misused by an AI agent, as it merely exposes group member information without enabling destructive or financial actions.
From the tool's definition Tool description states 'Retrieves the complete member list' — a pure read operation with no modification or side effects. The verb 'Retrieves' indicates data access only.
Attacks that exploit this kind of access
Retrieves the complete member list of an existing group chat in RongCloud. It is categorised as a Read tool in the RongCloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RongCloud MCP Server MCP server in PolicyLayer and add a rule for get_group_members: 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 RongCloud MCP Server. Nothing to install.
get_group_members 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_members 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_members. 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_members is provided by the RongCloud MCP Server MCP server (rongcloud/rongcloud-server-mcp-python). 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 →