Manage Grafana alerting routing configuration, including notification policies, contact points and time intervals. Notification policies define how alerts are grouped, routed, and which contact points receive them. Time intervals define active/mute periods for alert notifications. When to use: ...
Single-target operation
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_routing 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_routing 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_routing:
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_routing 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 alerting routing configuration, including notification policies, contact points and time intervals. Notification policies define how alerts are grouped, routed, and which contact points receive them. Time intervals define active/mute periods for alert notifications. When to use: - Understanding how alerts are routed to contact points/receivers - Debugging why an alert went to a specific receiver - Checking grouping, timing, or mute interval settings When NOT to use: - Checking alert rule configuration or state (use alerting_manage_rules). 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_routing. 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_routing 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_routing 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_routing. 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_routing 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