# add_activity_to_incident Add a note (userNote activity) to an existing incident\ Agent View of the PolicyLayer registry record for `add_activity_to_incident`. HTML page: https://policylayer.com/tools/0xteamhq-mcp-grafana/add-activity-to-incident ## Facts - Tool: `add_activity_to_incident` - Server: Grafana MCP Server (`0xteamhq/mcp-grafana`) — https://policylayer.com/tools/0xteamhq-mcp-grafana.md - Homepage: https://github.com/0xteamhq/mcp-grafana - Risk category: Write (Medium risk) - Registry record: grade C, identity unverified - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Rate-limited ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "add_activity_to_incident", "arguments": {} } } ``` ## 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 own 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." ## Use case 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. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Grafana MCP Server: ```json { "version": "1", "default": "deny", "tools": { "add_activity_to_incident": { "limits": [ { "counter": "add_activity_to_incident_rate", "window": "minute", "max": 30, "scope": "grant" } ] } } } ``` ## Other tools on Grafana MCP Server (42) - `query_loki_logs` — Execute — https://policylayer.com/tools/0xteamhq-mcp-grafana/query-loki-logs.md - `fetch_pyroscope_profile` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/fetch-pyroscope-profile.md - `find_error_pattern_logs` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/find-error-pattern-logs.md - `find_slow_requests` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/find-slow-requests.md - `generate_deeplink` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/generate-deeplink.md - `get_alert_rule_by_uid` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/get-alert-rule-by-uid.md - `get_assertions` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/get-assertions.md - `get_current_oncall_users` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/get-current-oncall-users.md - `get_dashboard_by_uid` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/get-dashboard-by-uid.md - `get_dashboard_panel_queries` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/get-dashboard-panel-queries.md - `get_dashboard_property` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/get-dashboard-property.md - `get_dashboard_summary` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/get-dashboard-summary.md - `get_datasource_by_name` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/get-datasource-by-name.md - `get_datasource_by_uid` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/get-datasource-by-uid.md - `get_incident` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/get-incident.md - `get_oncall_shift` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/get-oncall-shift.md - `get_sift_analysis` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/get-sift-analysis.md - `get_sift_investigation` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/get-sift-investigation.md - `list_alert_rules` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/list-alert-rules.md - `list_contact_points` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/list-contact-points.md - `list_datasources` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/list-datasources.md - `list_incidents` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/list-incidents.md - `list_loki_label_names` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/list-loki-label-names.md - `list_loki_label_values` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/list-loki-label-values.md - `list_oncall_schedules` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/list-oncall-schedules.md - `list_oncall_teams` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/list-oncall-teams.md - `list_oncall_users` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/list-oncall-users.md - `list_prometheus_label_names` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/list-prometheus-label-names.md - `list_prometheus_label_values` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/list-prometheus-label-values.md - `list_prometheus_metric_metadata` — Read — https://policylayer.com/tools/0xteamhq-mcp-grafana/list-prometheus-metric-metadata.md - …and 12 more: https://policylayer.com/tools/0xteamhq-mcp-grafana.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0xteamhq-mcp-grafana · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xteamhq-mcp-grafana