Manage Grafana alert rules with full CRUD capabilities and filtering. When to use: - Understanding why an alert is or isn't firing - Auditing alert rule configuration (queries, conditions, labels, notification settings) - Finding alert rules by state, folder, group, or name - Creating, updating,...
Accepts freeform code/query input (data[].model.expression); High parameter count (60 properties)
Part of the Mcp Grafana Npx MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use alerting_manage_rules to create or modify resources in Mcp Grafana Npx. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call alerting_manage_rules repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mcp Grafana Npx.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
alerting_manage_rules:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Mcp Grafana Npx policy for all 50 tools.
Agents calling write-class tools like alerting_manage_rules have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Manage Grafana alert rules with full CRUD capabilities and filtering. When to use: - Understanding why an alert is or isn't firing - Auditing alert rule configuration (queries, conditions, labels, notification settings) - Finding alert rules by state, folder, group, or name - Creating, updating, or deleting alert rules - Comparing rule versions to see what changed When NOT to use: - Checking how alerts are routed to receivers (use alerting_manage_routing). It is categorised as a Write tool in the Mcp Grafana Npx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for alerting_manage_rules. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Grafana Npx MCP server.
alerting_manage_rules 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 alerting_manage_rules rule in your Intercept 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 Intercept policy for alerting_manage_rules. 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.
alerting_manage_rules is provided by the Mcp Grafana Npx MCP server (mcp-grafana-npx). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept