Obtém a lista de webhooks configurados para uma sessão na Zappaz API
AI agents call get_webhooks to retrieve information from Zappaz MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves webhook configuration information from the Zappaz API, which is a data query operation with no side effects. However, severity is elevated to 'medium' rather than 'low' because webhooks can be sensitive infrastructure configuration data that reveals integration points and URLs where WhatsApp events are being sent, which could be valuable to an attacker for reconnaissance or for understanding the…
From the tool's definition Tool name 'get_webhooks' and description 'Obtém a lista de webhooks configurados' (retrieves the list of configured webhooks) indicate a read/query operation that retrieves webhook configuration data without modification.
Attacks that exploit this kind of access
Obtém a lista de webhooks configurados para uma sessão na Zappaz API. It is categorised as a Read tool in the Zappaz MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zappaz MCP Server MCP server in PolicyLayer and add a rule for get_webhooks: 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 Zappaz MCP Server. Nothing to install.
get_webhooks 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_webhooks 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_webhooks. 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_webhooks is provided by the Zappaz MCP Server MCP server (viiniolliveira/zappaz-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 →