Get the list of supported webhook event types.
AI agents call list_webhook_events to retrieve information from Localization without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns metadata about available webhook events. It performs a read-only lookup operation with no capability to modify, delete, or execute actions. The blast radius of misuse is minimal — an AI agent obtaining this list cannot cause harm beyond information disclosure of event type names, which is typically non-sensitive infrastructure documentation.
From the tool's definition Tool name is 'list_webhook_events' and description states 'Get the list of supported webhook event types' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get the list of supported webhook event types. It is categorised as a Read tool in the Localization MCP Server, which means it retrieves data without modifying state.
Register the Localization MCP server in PolicyLayer and add a rule for list_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 Localization. Nothing to install.
list_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 list_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 list_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.
list_webhook_events is provided by the Localization MCP server (localization-mcp-server). 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 →