AI agents call get_status to retrieve information from WhatsApp Web MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and pattern of sibling tools indicate a read-only query operation. No creation, modification, deletion, or external code execution is implied. The empty description reduces confidence slightly, but the naming convention and server context strongly suggest status retrieval functionality with no side effects.
From the tool's definition Tool name 'get_status' suggests retrieving status information. Given the WhatsApp Web MCP context with other tools like 'get_chats', 'get_messages', 'get_group_messages', and 'search_contacts', this tool likely retrieves user or chat status without…
Documented attack patterns abuse exactly the kind of access get_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WhatsApp Web MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_status": {}
}
}get_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_status. It is categorised as a Read tool in the WhatsApp Web MCP MCP Server, which means it retrieves data without modifying state.
Register the WhatsApp Web MCP server in PolicyLayer and add a rule for get_status: 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 WhatsApp Web MCP. Nothing to install.
get_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_status 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 get_status. 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.
get_status is provided by the WhatsApp Web MCP server (pnizer/wweb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 WhatsApp Web MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 WhatsApp Web MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.