whatsapp_mark_message_read · WSAPI WhatsApp MCP Server MCP

WHAT IT DOES

What whatsapp_mark_message_read does on WSAPI WhatsApp MCP Server

AI agents use whatsapp_mark_message_read to create or update resources in WSAPI WhatsApp MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WSAPI WhatsApp MCP Server environment.

WHY IT NEEDS A POLICY

Why whatsapp_mark_message_read needs a policy

This tool performs a reversible state modification to message read status, which qualifies as Write rather than Read. While the operation itself is non-destructive and has limited blast radius compared to other tools on this server (e.g., whatsapp_clear_chat or whatsapp_delete_message), it still modifies data state that could affect chat behavior and user experience.

From the tool's definition The tool name 'whatsapp_mark_message_read' indicates it modifies the read status of a message, changing its state from unread to read. The description 'Mark a message as read' confirms this is a state-modifying operation on message metadata.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

whatsapp_mark_message_read Rate-limited

whatsapp_mark_message_read stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "whatsapp_mark_message_read": {
      "limits": [
        {
          "counter": "whatsapp_mark_message_read_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches WSAPI WhatsApp MCP Server, so you can run agents against it safely.

FAQ

Questions about whatsapp_mark_message_read

What does the whatsapp_mark_message_read tool do? +

Mark a message as read. It is categorised as a Write tool in the WSAPI WhatsApp MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on whatsapp_mark_message_read? +

Register the WSAPI WhatsApp MCP Server MCP server in PolicyLayer and add a rule for whatsapp_mark_message_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 WSAPI WhatsApp MCP Server. Nothing to install.

What risk level is whatsapp_mark_message_read? +

whatsapp_mark_message_read is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit whatsapp_mark_message_read? +

Yes. Add a rate_limit block to the whatsapp_mark_message_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.

How do I block whatsapp_mark_message_read completely? +

Set action: deny in the PolicyLayer policy for whatsapp_mark_message_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.

What MCP server provides whatsapp_mark_message_read? +

whatsapp_mark_message_read is provided by the WSAPI WhatsApp MCP Server MCP server (wsapi-chat/wsapi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.