wa_group_handle_request
Approve or reject a pending join request for a WhatsApp group.
This record as markdown: /tools/delltrak-wamcp/wa-group-handle-request.md
What wa_group_handle_request does on WA MCP
AI agents use wa_group_handle_request to create or update resources in WA MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WA MCP environment.
Why wa_group_handle_request is rated Medium
This tool creates or modifies group membership state reversibly. While it affects group composition, the action can be undone (a rejected member can request again, an approved member can be removed). This places it in Write rather than Execute, as it does not run arbitrary code or trigger external side effects beyond membership modification. It is not Destructive because membership changes are reversible.
From the tool's definition Tool description states it 'Approve or reject a pending join request for a WhatsApp group.' This modifies group membership state by accepting or declining a request, which is a reversible action that changes data (group membership list).
Attacks that exploit this kind of access
The rule that runs wa_group_handle_request safely
PolicyLayer is an MCP gateway: it sits between your AI agents and WA MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wa_group_handle_request, this is the rule to start with:
wa_group_handle_request stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect WA MCP, apply this rule, and every wa_group_handle_request call is checked against it from then on.
Questions about wa_group_handle_request
Approve or reject a pending join request for a WhatsApp group. It is categorised as a Write tool in the WA MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WA MCP server in PolicyLayer and add a rule for wa_group_handle_request: 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 WA MCP. Nothing to install.
wa_group_handle_request 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 wa_group_handle_request 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 wa_group_handle_request. 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.
wa_group_handle_request is provided by the WA MCP server (delltrak/wamcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on WA, and thousands of servers like it.
This server
Across the catalogue