Verifica o status da conexão da instância WhatsApp.
AI agents call get_connection_status to retrieve information from Evolution API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only checks and reports the current connection status of a WhatsApp instance. It performs no side effects, creates no data modifications, executes no external commands, and poses minimal risk if misused by an AI agent. Status queries are inherently read-only operations.
From the tool's definition Tool name 'get_connection_status' and description 'Verifica o status da conexão da instância WhatsApp' (Verifies the connection status of the WhatsApp instance) indicate a query operation that retrieves status information without modifying or executing…
Attacks that exploit this kind of access
Verifica o status da conexão da instância WhatsApp. It is categorised as a Read tool in the Evolution API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Evolution API MCP Server MCP server in PolicyLayer and add a rule for get_connection_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 Evolution API MCP Server. Nothing to install.
get_connection_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_connection_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_connection_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_connection_status is provided by the Evolution API MCP Server MCP server (pablobispo/evoapi-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 →