add_activity_to_incident
Add a note (userNote activity) to an existing incident\
This record as markdown: /tools/0xteamhq-mcp-grafana/add-activity-to-incident.md
What add_activity_to_incident does on Grafana MCP Server
AI agents use add_activity_to_incident to create or update resources in Grafana MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Grafana MCP Server environment.
Why add_activity_to_incident is rated Medium
This tool creates new data (a note activity) within an incident, which is reversible through deletion or editing. It modifies the incident by appending information but does not execute code, delete data, or affect financial systems.
From the tool's definition Tool name 'add_activity_to_incident' and description 'Add a note (userNote activity) to an existing incident' indicate creation of new content (a note/activity) within an incident record.
Attacks that exploit this kind of access
The rule that runs add_activity_to_incident safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Grafana MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_activity_to_incident, this is the rule to start with:
add_activity_to_incident stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Grafana MCP Server, apply this rule, and every add_activity_to_incident call is checked against it from then on.
Questions about add_activity_to_incident
Add a note (userNote activity) to an existing incident\. It is categorised as a Write tool in the Grafana MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Grafana MCP Server MCP server in PolicyLayer and add a rule for add_activity_to_incident: 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 Grafana MCP Server. Nothing to install.
add_activity_to_incident 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 add_activity_to_incident 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 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.
add_activity_to_incident is provided by the Grafana MCP Server MCP server (0xteamhq/mcp-grafana). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Grafana MCP Server, and thousands of servers like it.
This server
Across the catalogue