Get community sub-groups.
AI agents call whatsapp_get_community_sub_groups to retrieve information from WSAPI WhatsApp MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about community sub-groups without creating, modifying, deleting, or executing any actions. It is a straightforward read operation that queries existing data structures. Even in the context of a WhatsApp management system, merely fetching group information poses minimal risk as it has no side effects on the system state or user data.
From the tool's definition Tool name contains 'get' and description states 'Get community sub-groups', indicating data retrieval with no modification or deletion.
Attacks that exploit this kind of access
Get community sub-groups. It is categorised as a Read tool in the WSAPI WhatsApp MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WSAPI WhatsApp MCP Server MCP server in PolicyLayer and add a rule for whatsapp_get_community_sub_groups: 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_get_community_sub_groups 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 whatsapp_get_community_sub_groups 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_get_community_sub_groups. 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_get_community_sub_groups 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 →