webhooks_list_event_types
List the known event type strings emitted across modules (cms, crm, kb, conv, outreach, system). Use the returned strings as input to webhooks_create. The subscription accepts arbitrary strings, so future event types work without a tool update — but this is the canonical catalog today.
This record as markdown: /tools/com-getmunin-munin/webhooks-list-event-types.md
What webhooks_list_event_types does on Munin
AI agents call webhooks_list_event_types to retrieve information from Munin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why webhooks_list_event_types is rated Low
This tool retrieves and enumerates existing event type definitions across multiple modules (cms, crm, kb, conv, outreach, system). It performs read-only introspection with no ability to create, modify, delete, or execute operations. The returned data is informational only and serves as input documentation for other tools like webhooks_create.
From the tool's definition Tool name contains 'list' and description states 'List the known event type strings' — a retrieval operation with no side effects. Returns a catalog of event types for reference.
Attacks that exploit this kind of access
The rule that runs webhooks_list_event_types safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Munin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For webhooks_list_event_types, this is the rule to start with:
webhooks_list_event_types is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every webhooks_list_event_types call is checked against it from then on.
Questions about webhooks_list_event_types
List the known event type strings emitted across modules (cms, crm, kb, conv, outreach, system). Use the returned strings as input to webhooks_create. The subscription accepts arbitrary strings, so future event types work without a tool update — but this is the canonical catalog today. It is categorised as a Read tool in the Munin MCP Server, which means it retrieves data without modifying state.
Register the Munin MCP server in PolicyLayer and add a rule for webhooks_list_event_types: 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 Munin. Nothing to install.
webhooks_list_event_types 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 webhooks_list_event_types 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 webhooks_list_event_types. 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.
webhooks_list_event_types is provided by the Munin MCP server (https://mcp.getmunin.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Munin, and thousands of servers like it.
This server
Across the catalogue