delete_notification_policies

delete_notification_policies

Server Mcp Read Only Grafana lukleh/mcp-read-only-grafana
Category Destructive
Risk class Critical
Parameters 00 required

What delete_notification_policies does on Mcp Read Only Grafana

AI agents call delete_notification_policies 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.

Why delete_notification_policies needs a policy

Deleting notification policies is an irreversible, destructive action that cannot be undone and removes critical configurations governing alert notifications. This falls clearly under the Destructive category. Severity is high because misconfiguration or unintended deletion could disable alerting infrastructure for an entire Grafana instance, impacting monitoring and incident response.

From the tool's definition Tool name 'delete_notification_policies' explicitly indicates deletion of notification policies. The server description notes separate 'write-capable commands for mutations' and sibling tools include other delete operations (delete_alert_rule,…

Questions about delete_notification_policies

What does the delete_notification_policies tool do? +

delete_notification_policies. 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.

How do I enforce a policy on delete_notification_policies? +

Register the Mcp Read Only Grafana MCP server in PolicyLayer and add a rule for delete_notification_policies: 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.

What risk level is delete_notification_policies? +

delete_notification_policies is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_notification_policies? +

Yes. Add a rate_limit block to the delete_notification_policies 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.

How do I block delete_notification_policies completely? +

Set action: deny in the PolicyLayer policy for delete_notification_policies. 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.

What MCP server provides delete_notification_policies? +

delete_notification_policies 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.