whatsapp_update_group_requests

WHAT IT DOES

What whatsapp_update_group_requests does on WSAPI WhatsApp MCP Server

AI agents use whatsapp_update_group_requests to create or update resources in WSAPI WhatsApp MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WSAPI WhatsApp MCP Server environment.

WHY IT NEEDS A POLICY

Why whatsapp_update_group_requests needs a policy

This tool modifies group membership state by accepting or denying requests, which is reversible (requests can typically be resubmitted). It is not destructive (requests aren't permanently deleted), not financial, and not a simple read operation.

From the tool's definition Tool description states 'Approve or reject pending join requests.' The verbs 'approve' and 'reject' are write-class operations that modify the state of pending requests within a WhatsApp group.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

whatsapp_update_group_requests Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "whatsapp_update_group_requests": {
      "limits": [
        {
          "counter": "whatsapp_update_group_requests_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches WSAPI WhatsApp MCP Server, so you can run agents against it safely.

FAQ

Questions about whatsapp_update_group_requests

What does the whatsapp_update_group_requests tool do? +

Approve or reject pending join requests. It is categorised as a Write tool in the WSAPI WhatsApp MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on whatsapp_update_group_requests? +

Register the WSAPI WhatsApp MCP Server MCP server in PolicyLayer and add a rule for whatsapp_update_group_requests: 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 WSAPI WhatsApp MCP Server. Nothing to install.

What risk level is whatsapp_update_group_requests? +

whatsapp_update_group_requests is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit whatsapp_update_group_requests? +

Yes. Add a rate_limit block to the whatsapp_update_group_requests 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 whatsapp_update_group_requests completely? +

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

whatsapp_update_group_requests is provided by the WSAPI WhatsApp MCP Server MCP server (wsapi-chat/wsapi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.