webhooks_update
Patch a webhook subscription. Pass only the fields you want to change. Replacing
This record as markdown: /tools/com-getmunin-munin/webhooks-update.md
What webhooks_update does on Munin
AI agents use webhooks_update to create or update resources in Munin, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Munin environment.
Why webhooks_update is rated Medium
The tool modifies existing webhook configuration in the system. While webhooks control external integrations and their misconfiguration could have downstream effects, the operation is reversible (webhooks can be patched back to previous states). This qualifies as Write rather than Execute because it changes data/configuration directly rather than triggering immediate external actions.
From the tool's definition webhooks_update patches/modifies a webhook subscription configuration. The description indicates this is a reversible update operation ('Patch a webhook subscription. Pass only the fields you want to change. Replacing').
Attacks that exploit this kind of access
The rule that runs webhooks_update 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_update, this is the rule to start with:
webhooks_update stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_update call is checked against it from then on.
Questions about webhooks_update
Patch a webhook subscription. Pass only the fields you want to change. Replacing. It is categorised as a Write tool in the Munin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Munin MCP server in PolicyLayer and add a rule for webhooks_update: 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_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the webhooks_update 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_update. 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_update 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