AI agents invoke send_typing to trigger actions in Wa Bridge. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Sending a presence/typing indicator is an external side-effecting action on the WhatsApp platform. It doesn't read or write persistent data, but it executes an operation that changes the visible state for other participants. It's not destructive or financial, but it does trigger a real-time external operation, placing it in Execute.
From the tool's definition 'Send a presence indicator' — triggers an external operation on WhatsApp (typing/presence state) that affects what other users see in real time
Attacks that exploit this kind of access
Send a presence indicator. State. It is categorised as a Execute tool in the Wa Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Wa Bridge MCP server in PolicyLayer and add a rule for send_typing: 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.
send_typing is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the send_typing 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 send_typing. 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.
send_typing 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 →