Get delivery events for a specific webhook. Shows recent event deliveries, their status, and response codes.
AI agents call get_webhook_events to retrieve information from Payoza 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 and queries webhook event data—specifically delivery status, timestamps, and response codes. It has no side effects, does not modify data, and does not execute external operations or move funds. It is purely informational, making it a Read category tool with low severity since the blast radius of misuse is limited to information disclosure of webhook event logs.
From the tool's definition Tool name 'get_webhook_events' and description 'Get delivery events for a specific webhook. Shows recent event deliveries, their status, and response codes' indicate retrieval of historical webhook delivery information without modification.
Attacks that exploit this kind of access
Get delivery events for a specific webhook. Shows recent event deliveries, their status, and response codes. It is categorised as a Read tool in the Payoza MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Payoza MCP Server MCP server in PolicyLayer and add a rule for get_webhook_events: 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 Payoza MCP Server. Nothing to install.
get_webhook_events 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_webhook_events 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_webhook_events. 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_webhook_events is provided by the Payoza MCP Server MCP server (payoza/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 →