create_alert_rule
AI agents use create_alert_rule to create or update resources in Mcp Read Only Grafana — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Read Only Grafana environment.
This tool creates alert rules in Grafana, which modifies system state. Creating alert rules can trigger notifications, escalations, and automated responses, making it impactful but reversible. It fits Write category—not Destructive (is reversible via delete), not Execute (doesn't run arbitrary code), not Financial.
From the tool's definition Tool name 'create_alert_rule' and context from sibling 'delete_alert_rule' indicate this is a mutation operation. Server description states it has 'write-capable command for mutations.' Empty tool description limits confidence slightly.
Attacks that exploit this kind of access
create_alert_rule. It is categorised as a Write tool in the Mcp Read Only Grafana MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Read Only Grafana MCP server in PolicyLayer and add a rule for create_alert_rule: 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.
create_alert_rule 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 create_alert_rule 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 create_alert_rule. 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.
create_alert_rule 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 →