AI agents use whatsapp_auto_reply_disable to create or update resources in Waha — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Waha environment.
This tool modifies WhatsApp account configuration settings by disabling an auto-reply feature for a specific contact. It is a Write operation because it changes system state (disables a setting) in a reversible manner—the setting can be re-enabled. It is not Destructive because the underlying auto-reply rule is not deleted, only disabled.
From the tool's definition Tool name 'whatsapp_auto_reply_disable' and description 'Disable auto-reply with audio transcription for a contact' indicate modification of account/contact settings. The action disables (modifies) an existing auto-reply configuration, which is reversible.
Attacks that exploit this kind of access
Disable auto-reply with audio transcription for a contact. Args: - phone: Phone number digits only, no @, no spaces (e.g.,. It is categorised as a Write tool in the Waha MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Waha MCP server in PolicyLayer and add a rule for whatsapp_auto_reply_disable: 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. Nothing to install.
whatsapp_auto_reply_disable 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_auto_reply_disable 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_auto_reply_disable. 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_auto_reply_disable is provided by the Waha MCP server (@marcos-heidemann/waha-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 →