Add an emoji reaction to a message. To remove a reaction, send an empty string.
AI agents use waha_react_to_message to create or update resources in WAHA MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WAHA MCP Server environment.
This tool modifies an existing message by adding or removing an emoji reaction. It creates or updates reaction data on a message, which is reversible (reactions can be added or removed). This fits the Write category — no code execution, no irreversible deletion, and no financial implications.
From the tool's definition Add an emoji reaction to a message. To remove a reaction, send an empty string.
Documented attack patterns abuse exactly the kind of access waha_react_to_message gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WAHA MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for waha_react_to_message:
{
"version": "1",
"default": "deny",
"tools": {
"waha_react_to_message": {
"limits": [
{
"counter": "waha_react_to_message_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} waha_react_to_message 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.
Free to start. No card required.
Add an emoji reaction to a message. To remove a reaction, send an empty string. It is categorised as a Write tool in the WAHA MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WAHA MCP Server MCP server in PolicyLayer and add a rule for waha_react_to_message: 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 WAHA MCP Server. Nothing to install.
waha_react_to_message 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 waha_react_to_message 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 waha_react_to_message. 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.
waha_react_to_message is provided by the WAHA MCP Server MCP server (seejux/waha-whatsapp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WAHA MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
52 WAHA MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.