Subscribe to presence updates for a chat.
AI agents call whatsapp_subscribe_chat_presence to retrieve information from WSAPI WhatsApp MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Subscribing to presence updates is a read/monitoring operation that retrieves real-time status information (online/offline) for a chat. It registers interest in data but does not create, modify, or delete any data. However, it does trigger an external operation on WhatsApp's side, so there's slight ambiguity; nonetheless the primary effect is receiving data, making Read the most appropriate category.
From the tool's definition Subscribe to presence updates for a chat
Attacks that exploit this kind of access
Subscribe to presence updates for a chat. It is categorised as a Read tool in the WSAPI WhatsApp MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WSAPI WhatsApp MCP Server MCP server in PolicyLayer and add a rule for whatsapp_subscribe_chat_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.
whatsapp_subscribe_chat_presence is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the whatsapp_subscribe_chat_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.
Set action: deny in the PolicyLayer policy for whatsapp_subscribe_chat_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.
whatsapp_subscribe_chat_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →