Get QR code text string for WhatsApp login.
AI agents call whatsapp_get_qr_code 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.
This tool retrieves a QR code string used for authentication. While it reads rather than modifies data, the severity is elevated to 'medium' because the QR code is sensitive authentication material that could enable unauthorized WhatsApp account access if obtained by a malicious agent or intercepted. The blast radius includes potential account compromise and impersonation.
From the tool's definition Tool description states "Get QR code text string for WhatsApp login" — this retrieves login credentials/authentication data. The operation is read-only with no data modification.
Attacks that exploit this kind of access
Get QR code text string for WhatsApp login. 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_get_qr_code: 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_get_qr_code 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_get_qr_code 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_get_qr_code. 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_get_qr_code 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 →