List all WhatsApp instances
AI agents call list_instances to retrieve information from Evolution API 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 queries and returns information about existing WhatsApp instances without modifying, deleting, or executing any operations. It is a straightforward enumeration/retrieval function typical of Read category tools. The severity is low because listing instances poses minimal risk—it merely exposes metadata about configurations without enabling harmful actions on those instances.
From the tool's definition Tool name 'list_instances' and description 'List all WhatsApp instances' indicate a retrieval operation with no side effects. The verb 'list' is explicitly identified in the Read category guidelines.
Attacks that exploit this kind of access
List all WhatsApp instances. It is categorised as a Read tool in the Evolution API WhatsApp MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Evolution API WhatsApp MCP Server MCP server in PolicyLayer and add a rule for list_instances: 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 Evolution API WhatsApp MCP Server. Nothing to install.
list_instances 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 list_instances 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 list_instances. 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.
list_instances is provided by the Evolution API WhatsApp MCP Server MCP server (luiso2/mcp-evolution-api). 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 →