Removes one or more users from a RongCloud group chat.
AI agents use quit_group to create or update resources in RongCloud MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RongCloud MCP Server environment.
Removing users from a group chat is a reversible write operation — users can be re-added. It modifies group membership state but does not permanently delete data or the group itself. The blast radius is medium since an AI agent could erroneously remove legitimate members from group conversations.
From the tool's definition Removes one or more users from a RongCloud group chat
Attacks that exploit this kind of access
Removes one or more users from a RongCloud group chat. It is categorised as a Write tool in the RongCloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RongCloud MCP Server MCP server in PolicyLayer and add a rule for quit_group: 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.
quit_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the quit_group 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 quit_group. 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.
quit_group 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 →