Mark a message as read.
AI agents use mark_message_as_read to create or update resources in PyWA MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PyWA MCP Server environment.
This tool modifies message state (marking as read) which is a reversible write operation. It does not retrieve data (Read), execute arbitrary code (Execute), permanently delete data (Destructive), or move money (Financial). The blast radius is minimal—changing read status is a benign metadata update with no harmful side effects if misused by an agent.
From the tool's definition Tool name 'mark_message_as_read' and description 'Mark a message as read' indicate a state modification operation on WhatsApp messages. This updates message metadata (read status) rather than retrieving data.
Attacks that exploit this kind of access
Mark a message as read. It is categorised as a Write tool in the PyWA MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PyWA MCP Server MCP server in PolicyLayer and add a rule for mark_message_as_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 PyWA MCP Server. Nothing to install.
mark_message_as_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_message_as_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_message_as_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_message_as_read is provided by the PyWA MCP Server MCP server (jem-hr/pywa-mcp-server). 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 →