AI agents use mark_read 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.
This tool modifies message metadata on the WhatsApp platform by changing read status, which is a Write operation. It affects external state (sender perception via blue ticks) and could be misused by an AI agent to manipulate conversation history visibility or deceive message senders about engagement. However, it is reversible and does not delete or financially harm anyone, so it ranks below Destructive and Financial.
From the tool's definition Tool name 'mark_read' and description 'Mark a list of inbound messages as read on the WhatsApp side (sender sees blue ticks)' — this modifies state (message read status) and affects visual feedback to other users, but the change is reversible (messages can be…
Attacks that exploit this kind of access
Mark a list of inbound messages as read on the WhatsApp side (sender sees blue ticks). 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 mark_read: 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.
mark_read 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 mark_read 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 mark_read. 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.
mark_read 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 →