AI agents call get_group_by_id 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.
This tool retrieves group information without modifying, deleting, or executing code. It falls squarely into the Read category as a data retrieval operation. Severity is medium rather than low because unauthorized access to WhatsApp group metadata could expose private group information, membership lists, and communication patterns to an AI agent without proper authorization controls.
From the tool's definition Tool name 'get_group_by_id' indicates a retrieval operation that queries group data by identifier. The sibling tools include read-only operations like 'get_chats', 'get_group_messages', 'get_messages', 'search_contacts', and 'search_groups', establishing a…
Documented attack patterns abuse exactly the kind of access get_group_by_id 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_group_by_id:
{
"version": "1",
"default": "deny",
"tools": {
"get_group_by_id": {}
}
}get_group_by_id 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_group_by_id. 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_group_by_id: 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_group_by_id 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_group_by_id 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_group_by_id. 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_group_by_id 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.