Remove a participant from a WhatsApp group
AI agents call remove_group_participant to permanently remove resources in Mcp Afip — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a participant from a group is a destructive, hard-to-reverse action: the participant loses access immediately and must be explicitly re-added. This warrants the Destructive category. Severity is medium since it affects group membership rather than financial or critical data, but misuse by an AI agent could cause unintended removal of users from communication channels.
From the tool's definition "Remove a participant from a WhatsApp group" — removing a participant is an irreversible action that expels a user from the group
Documented attack patterns abuse exactly the kind of access remove_group_participant gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Afip, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_group_participant:
{
"version": "1",
"default": "deny",
"hide": [
"remove_group_participant"
]
} remove_group_participant disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a participant from a WhatsApp group. It is categorised as a Destructive tool in the Mcp Afip MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for remove_group_participant: 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 Mcp Afip. Nothing to install.
remove_group_participant 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 remove_group_participant 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 remove_group_participant. 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.
remove_group_participant is provided by the Mcp Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Afip, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Afip tools catalogued and risk-classified — across an index of 43,000+ MCP servers.