Medium Risk

add_activity_to_incident

Add a note (userNote activity) to an existing incident's timeline using its ID. The note body can include URLs which will be attached as context. Use this to add context to an incident.

Accepts raw HTML/template content (body)

Part of the Mcp Grafana Npx MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

mcp-grafana-npx Write Risk 2/5

AI agents use add_activity_to_incident 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 add_activity_to_incident 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.

mcp-grafana-npx.yaml
tools:
  add_activity_to_incident:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Mcp Grafana Npx policy for all 50 tools.

Tool Name add_activity_to_incident
Category Write
Risk Level Medium

View all 50 tools →

Agents calling write-class tools like add_activity_to_incident have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the add_activity_to_incident tool do? +

Add a note (userNote activity) to an existing incident's timeline using its ID. The note body can include URLs which will be attached as context. Use this to add context to an incident.. 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.

How do I enforce a policy on add_activity_to_incident? +

Add a rule in your Intercept YAML policy under the tools section for add_activity_to_incident. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Grafana Npx MCP server.

What risk level is add_activity_to_incident? +

add_activity_to_incident is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_activity_to_incident? +

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

How do I block add_activity_to_incident completely? +

Set action: deny in the Intercept policy for add_activity_to_incident. 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 add_activity_to_incident? +

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

Enforce policies on Mcp Grafana Npx

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.