Get RSVP statistics for a WhatsApp event
AI agents call get_event_stats to retrieve information from WhatsApp MCP Automation without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries event RSVP statistics without modifying, deleting, or executing external operations. It is a read-only query operation with minimal security risk—the worst case being unauthorized access to event attendance information, which is typically visible to event participants anyway. Low severity due to limited blast radius and no irreversible effects.
From the tool's definition Tool name 'get_event_stats' with description 'Get RSVP statistics for a WhatsApp event' indicates retrieval of aggregate data about event responses with no modification or deletion of data.
Attacks that exploit this kind of access
Get RSVP statistics for a WhatsApp event. It is categorised as a Read tool in the WhatsApp MCP Automation MCP Server, which means it retrieves data without modifying state.
Register the WhatsApp MCP Automation MCP server in PolicyLayer and add a rule for get_event_stats: 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 WhatsApp MCP Automation. Nothing to install.
get_event_stats 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_event_stats 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_event_stats. 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_event_stats is provided by the WhatsApp MCP Automation MCP server (priyasogani8-star/whatsapp-mcp-automation). 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 →