whatsapp_set_presence · WSAPI WhatsApp MCP Server MCP

WHAT IT DOES

What whatsapp_set_presence does on WSAPI WhatsApp MCP Server

AI agents use whatsapp_set_presence 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_set_presence needs a policy

This tool modifies account metadata (presence state) reversibly. While it changes account state, the effect is cosmetic and poses minimal risk. It cannot delete data, execute arbitrary operations, or cause financial harm. The primary concern is minor misuse (e.g., repeatedly toggling presence), hence Write category with low severity.

From the tool's definition Tool performs 'Set account presence state' which modifies the user's presence status (available/unavailable). This is a state change operation that affects how the account appears to others but is reversible and has no data deletion or financial impact.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

whatsapp_set_presence Rate-limited

whatsapp_set_presence 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_set_presence": {
      "limits": [
        {
          "counter": "whatsapp_set_presence_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_set_presence

What does the whatsapp_set_presence tool do? +

Set account presence state (available or unavailable). 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_set_presence? +

Register the WSAPI WhatsApp MCP Server MCP server in PolicyLayer and add a rule for whatsapp_set_presence: 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_set_presence? +

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

Can I rate-limit whatsapp_set_presence? +

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

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

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