AI agents call get_message_status_updates to retrieve information from Whatsapp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the status of previously sent messages and returns information about delivery state. It performs no modifications, deletions, or execution of external operations. The data retrieved is already-existing message metadata that does not change as a result of the query. This is a passive read operation with minimal security risk.
From the tool's definition The tool 'get_message_status_updates' retrieves delivery status updates for sent messages with possible statuses of 'sent, delivered, read, failed'. The verb 'Get' and the focus on retrieving status information with no side effects indicate a read operation.
Attacks that exploit this kind of access
Get delivery status updates for sent messages (sent, delivered, read, failed). It is categorised as a Read tool in the Whatsapp MCP Server, which means it retrieves data without modifying state.
Register the Whatsapp MCP server in PolicyLayer and add a rule for get_message_status_updates: 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. Nothing to install.
get_message_status_updates 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_message_status_updates 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_message_status_updates. 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_message_status_updates is provided by the Whatsapp MCP server (spirit122/whatsapp-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 →