AI agents call get_session_status to retrieve information from Chatkazi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves session metadata (connection state, QR readiness status) for monitoring purposes. It has no side effects, does not modify data, and does not execute commands or trigger external actions beyond a simple status lookup. It is clearly a Read operation with minimal risk if misused by an AI agent—an agent could only learn the state of WhatsApp sessions, not alter them or cause damage.
From the tool's definition Tool name and description explicitly indicate a query operation: 'Check the current state of a specific WhatsApp session'. The verb 'check' and the word 'state' indicate information retrieval without side effects.
Attacks that exploit this kind of access
Check the current state of a specific WhatsApp session (e.g., connected, qr_ready). It is categorised as a Read tool in the Chatkazi MCP Server, which means it retrieves data without modifying state.
Register the Chatkazi MCP server in PolicyLayer and add a rule for get_session_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 Chatkazi. Nothing to install.
get_session_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_session_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_session_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_session_status is provided by the Chatkazi MCP server (lxmwaniky/chatkazi-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 →