zernio_reject_whatsapp_group_join_requests

What zernio_reject_whatsapp_group_join_requests does on Zernio

AI agents use zernio_reject_whatsapp_group_join_requests to create or update resources in Zernio, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zernio environment.

Why zernio_reject_whatsapp_group_join_requests is rated Medium

This tool modifies data (join request state) but does not permanently delete records or execute arbitrary operations. Rejecting requests is a reversible administrative action on WhatsApp group membership—the most severe category applicable is Write rather than Destructive (data is not purged) or Execute (no arbitrary code/external commands triggered).

From the tool's definition Tool description: 'Reject pending join requests for a WhatsApp Group.' The action of rejecting requests modifies the state of join request records by changing their status from pending to rejected, which is reversible (requests could theoretically be…

The rule that runs zernio_reject_whatsapp_group_join_requests safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Zernio, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zernio_reject_whatsapp_group_join_requests, this is the rule to start with:

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

Questions about zernio_reject_whatsapp_group_join_requests