Mute or unmute a chat.
AI agents use whatsapp_mute_chat 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.
This tool modifies a user's chat settings by changing the mute status—a reversible operation with no data deletion, destructive effects, code execution, or financial consequences. The blast radius is minimal since muting/unmuting only affects local notification preferences and can be easily reversed by the user or an AI agent.
From the tool's definition Tool name is 'whatsapp_mute_chat' and description states it will 'Mute or unmute a chat.' These are reversible modifications to chat notification settings.
Attacks that exploit this kind of access
Mute or unmute a chat. 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.
Register the WSAPI WhatsApp MCP Server MCP server in PolicyLayer and add a rule for whatsapp_mute_chat: 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.
whatsapp_mute_chat 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 whatsapp_mute_chat 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 whatsapp_mute_chat. 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.
whatsapp_mute_chat 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.
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 →