conv_rotate_widget_key
Revoke any active widget keys bound to this channel and mint a fresh
This record as markdown: /tools/com-getmunin-munin/conv-rotate-widget-key.md
What conv_rotate_widget_key does on Munin
AI agents call conv_rotate_widget_key to permanently remove resources in Munin, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why conv_rotate_widget_key is rated Critical
Revoking active keys is irreversible and breaks existing integrations relying on those keys.
From the tool's definition Revoke any active widget keys... mint a fresh
Attacks that exploit this kind of access
The rule that runs conv_rotate_widget_key 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 conv_rotate_widget_key, this is the rule to start with:
conv_rotate_widget_key is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every conv_rotate_widget_key call is checked against it from then on.
Questions about conv_rotate_widget_key
Revoke any active widget keys bound to this channel and mint a fresh. It is categorised as a Destructive tool in the Munin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Munin MCP server in PolicyLayer and add a rule for conv_rotate_widget_key: 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.
conv_rotate_widget_key is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the conv_rotate_widget_key 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 conv_rotate_widget_key. 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.
conv_rotate_widget_key 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.
Across the catalogue