Get contact details by JID.
AI agents call get_contact_by_id to retrieve information from WhatsApp MCP Stream without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves contact information from WhatsApp based on a JID (Jabber ID) identifier. It performs a simple lookup without creating, modifying, deleting, or executing operations. The blast radius is minimal—an agent could only expose existing contact data that would be visible to an authenticated WhatsApp user anyway. No destructive or financial impact is possible.
From the tool's definition Tool name 'get_contact_by_id' and description 'Get contact details by JID' indicate a retrieval operation with no side effects. The verb 'get' and lack of any modification language confirm this is a query-only action.
Attacks that exploit this kind of access
Get contact details by JID. It is categorised as a Read tool in the WhatsApp MCP Stream MCP Server, which means it retrieves data without modifying state.
Register the WhatsApp MCP Stream MCP server in PolicyLayer and add a rule for get_contact_by_id: 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 Stream. Nothing to install.
get_contact_by_id 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_contact_by_id 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_contact_by_id. 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_contact_by_id is provided by the WhatsApp MCP Stream MCP server (loglux/whatsapp-mcp-stream). 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 →