whatsapp_mark_chat_as_read · WSAPI WhatsApp MCP Server MCP

WHAT IT DOES

What whatsapp_mark_chat_as_read does on WSAPI WhatsApp MCP Server

AI agents use whatsapp_mark_chat_as_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_chat_as_read needs a policy

This tool modifies WhatsApp chat metadata (read/unread status) but does not delete data, execute external code, or create financial obligations. It is a reversible write operation that changes application state.

From the tool's definition Tool name "whatsapp_mark_chat_as_read" and description "Mark a chat as read or unread" indicate modification of chat state/metadata. The action changes the read status of a conversation, which is a reversible state modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

whatsapp_mark_chat_as_read Rate-limited

whatsapp_mark_chat_as_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_chat_as_read": {
      "limits": [
        {
          "counter": "whatsapp_mark_chat_as_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_chat_as_read

What does the whatsapp_mark_chat_as_read tool do? +

Mark a chat as read or unread. 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_chat_as_read? +

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

What risk level is whatsapp_mark_chat_as_read? +

whatsapp_mark_chat_as_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_chat_as_read? +

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

How do I block whatsapp_mark_chat_as_read completely? +

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

What MCP server provides whatsapp_mark_chat_as_read? +

whatsapp_mark_chat_as_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.

// THE FULL RECORD

whatsapp_mark_chat_as_read is one line of WSAPI WhatsApp MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →