delete_mute_timing
AI agents call delete_mute_timing to permanently remove resources in Mcp Read Only Grafana — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete' prefix establishes this as a Destructive action—it removes data that cannot be recovered without manual restoration or backups. In Grafana, mute timings control alert suppression schedules; deleting one could disrupt alert management workflows. This is more severe than Write (which is reversible) but less severe than Financial.
From the tool's definition Tool name is 'delete_mute_timing' with 'delete' prefix, indicating irreversible data removal. Server context shows sibling delete tools (delete_alert_rule, delete_contact_point, delete_notification_policies, delete_notification_template) that are destructive…
Attacks that exploit this kind of access
delete_mute_timing. It is categorised as a Destructive tool in the Mcp Read Only Grafana MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Read Only Grafana MCP server in PolicyLayer and add a rule for delete_mute_timing: 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 Mcp Read Only Grafana. Nothing to install.
delete_mute_timing 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 delete_mute_timing 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 delete_mute_timing. 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.
delete_mute_timing is provided by the Mcp Read Only Grafana MCP server (lukleh/mcp-read-only-grafana). 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 →