Mark two JIDs as the same person. After merging, list_conversations collapses them and read_conversation returns combined history regardless of which JID is queried. Pass the @lid form as alias and the @s.whatsapp.net form as canonical, so phone-number metadata is preserved.
AI agents use merge_jids to create or update resources in Wa Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wa Bridge environment.
The tool creates or modifies data (merging JID identities) in a reversible manner. While it affects how conversations are grouped and displayed, this is a metadata transformation rather than a destructive operation. The effects are reversible—aliases can be unmerged or reassigned. It does not execute arbitrary code, delete data irreversibly, or involve financial transactions.
From the tool's definition Tool description states 'Mark two JIDs as the same person' and 'After merging, list_conversations collapses them and read_conversation returns combined history'. These are reversible modifications to alias/contact metadata mappings.
Attacks that exploit this kind of access
Mark two JIDs as the same person. After merging, list_conversations collapses them and read_conversation returns combined history regardless of which JID is queried. Pass the @lid form as alias and the @s.whatsapp.net form as canonical, so phone-number metadata is preserved. It is categorised as a Write tool in the Wa Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wa Bridge MCP server in PolicyLayer and add a rule for merge_jids: 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 Wa Bridge. Nothing to install.
merge_jids is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the merge_jids 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 merge_jids. 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.
merge_jids is provided by the Wa Bridge MCP server (obirimensah05/whatsapp-bridge). 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 →