Check if the WhatsApp session is connected and working. Returns the session status (WORKING, STOPPED, etc.), the connected phone number, and display name. Use this to verify connectivity before sending messages. No parameters required. Returns: - name: Session name - status:
AI agents call whatsapp_session_status to retrieve information from Waha without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries state information about a WhatsApp session without modifying, executing commands, or performing any operations. It is a diagnostic/status check mechanism, placing it squarely in the Read category. Severity is low because the information returned (session status, phone number, display name) poses minimal risk if exposed or misused by an AI agent.
From the tool's definition Tool checks and returns session status (WORKING, STOPPED, etc.), connected phone number, and display name.
Attacks that exploit this kind of access
Check if the WhatsApp session is connected and working. Returns the session status (WORKING, STOPPED, etc.), the connected phone number, and display name. Use this to verify connectivity before sending messages. No parameters required. Returns: - name: Session name - status:. It is categorised as a Read tool in the Waha MCP Server, which means it retrieves data without modifying state.
Register the Waha MCP server in PolicyLayer and add a rule for whatsapp_session_status: 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 Waha. Nothing to install.
whatsapp_session_status 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_session_status 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_session_status. 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_session_status is provided by the Waha MCP server (@marcos-heidemann/waha-mcp-server). 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 →