High Risk →

leave_group

Leave a WhatsApp group

How to control leave_group ↓

What leave_group does on Mcp Afip

AI agents invoke leave_group to trigger actions in Mcp Afip. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Why leave_group needs a policy

Leaving a WhatsApp group is an external action with real-world side effects (removal from the group, loss of access to group messages). It is not purely reversible (rejoining requires an invite) and involves executing an operation on an external messaging platform. This fits Execute as the most appropriate category. The tool appears out of place on an AFIP/invoicing server, which lowers confidence slightly.

From the tool's definition 'Leave a WhatsApp group' — triggers an external operation (leaving a group) that changes membership state in WhatsApp

Documented attack patterns abuse exactly the kind of access leave_group gives an agent:

How to control leave_group

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 leave_group:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "leave_group": {
      "limits": [
        {
          "counter": "leave_group_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

leave_group stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Afip — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about leave_group

What does the leave_group tool do? +

Leave a WhatsApp group. It is categorised as a Execute tool in the Mcp Afip MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on leave_group? +

Register the Mcp Afip MCP server in PolicyLayer and add a rule for leave_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 Mcp Afip. Nothing to install.

What risk level is leave_group? +

leave_group is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit leave_group? +

Yes. Add a rate_limit block to the leave_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.

How do I block leave_group completely? +

Set action: deny in the PolicyLayer policy for leave_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.

What MCP server provides leave_group? +

leave_group 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.

Enforce policy on every Mcp Afip tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.