abs_zalo_kick_member
Remove a user/member from a group (Requires Group Admin or Owner rights). Note: Destructive action requires 2-step confirmation.
This record as markdown: /tools/abs-zalo-bot/abs-zalo-kick-member.md
What abs_zalo_kick_member does on Abs Zalo Bot
AI agents call abs_zalo_kick_member to permanently remove resources in Abs Zalo Bot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why abs_zalo_kick_member is rated Critical
An AI agent that decides to call abs_zalo_kick_member doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Abs Zalo Bot is gone. There is no undo for destructive operations.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs abs_zalo_kick_member safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Abs Zalo Bot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For abs_zalo_kick_member, this is the rule to start with:
abs_zalo_kick_member is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Abs Zalo Bot, apply this rule, and every abs_zalo_kick_member call is checked against it from then on.
Questions about abs_zalo_kick_member
Remove a user/member from a group (Requires Group Admin or Owner rights). Note: Destructive action requires 2-step confirmation. It is categorised as a Destructive tool in the Abs Zalo Bot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Abs Zalo Bot MCP server in PolicyLayer and add a rule for abs_zalo_kick_member: 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 Abs Zalo Bot. Nothing to install.
abs_zalo_kick_member is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the abs_zalo_kick_member 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 abs_zalo_kick_member. 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.
abs_zalo_kick_member is provided by the Abs Zalo Bot MCP server (abs-zalo-bot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Abs Zalo Bot, and thousands of servers like it.
Across the catalogue