List the WhatsApp CRM message use cases built into HelloGrowthCRM
AI agents call solutions_list_whatsapp_use_cases to retrieve information from Mcp Bot Crawler without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and displays existing CRM use case data without modifying, executing code, deleting data, or moving money. It performs a simple information lookup with no side effects, fitting the 'Read' category for data retrieval operations.
From the tool's definition Tool name and description indicate a listing operation: 'List the WhatsApp CRM message use cases' — this is a read-only query that retrieves pre-built use case information from HelloGrowthCRM.
Attacks that exploit this kind of access
List the WhatsApp CRM message use cases built into HelloGrowthCRM. It is categorised as a Read tool in the Mcp Bot Crawler MCP Server, which means it retrieves data without modifying state.
Register the Mcp Bot Crawler MCP server in PolicyLayer and add a rule for solutions_list_whatsapp_use_cases: 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 Mcp Bot Crawler. Nothing to install.
solutions_list_whatsapp_use_cases 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 solutions_list_whatsapp_use_cases 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 solutions_list_whatsapp_use_cases. 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.
solutions_list_whatsapp_use_cases is provided by the Mcp Bot Crawler MCP server (merulocal/hellogrowthcrmwebsite_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 →