Returns the current WhatsApp connection status. Call this first to verify the server is ready before calling other tools.
AI agents call get_status to retrieve information from WhatsApp MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely queries and returns the connection status of WhatsApp—a passive read operation with no side effects, no data modification, and no capability to execute commands or access sensitive chat data. It is a diagnostic/monitoring tool appropriate for checking service readiness before invoking other tools.
From the tool's definition Tool name 'get_status' and description 'Returns the current WhatsApp connection status' indicate a query operation that retrieves status information without modifying or executing actions.
Attacks that exploit this kind of access
Returns the current WhatsApp connection status. Call this first to verify the server is ready before calling other tools. It is categorised as a Read tool in the WhatsApp MCP MCP Server, which means it retrieves data without modifying state.
Register the WhatsApp MCP server in PolicyLayer and add a rule for get_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 WhatsApp MCP. Nothing to install.
get_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 get_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 get_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.
get_status is provided by the WhatsApp MCP server (ponmanian-sa/whatsapp_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 →