Get profile picture URL for a contact or group JID.
AI agents call get_profile_pic 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 is a read-only query operation that retrieves a profile picture URL. It has no side effects, does not modify data, and retrieves information that is typically public in WhatsApp (profile pictures are visible to contacts). The blast radius of misuse is minimal—an agent could only enumerate profile pictures of known JIDs, which poses no immediate harm.
From the tool's definition Tool name 'get_profile_pic' and description 'Get profile picture URL for a contact or group JID' indicate retrieval of publicly accessible profile metadata without modification or side effects.
Attacks that exploit this kind of access
Get profile picture URL for a contact or group 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_profile_pic: 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_profile_pic 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_profile_pic 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_profile_pic. 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_profile_pic 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 →