add_incident_note
Add a note to an incident. Internal notes are visible to your team only; public notes are posted to the status page for subscribers/customers. Markdown is supported.
This record as markdown: /tools/com-oneuptime-mcp/add-incident-note.md
What add_incident_note does on OneUptime
AI agents use add_incident_note to create or update resources in OneUptime, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OneUptime environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
note | string | Yes | The note content (Markdown supported). |
incidentId | string | Yes | UUID of the incident to annotate. |
visibility | string | — | Where the note is visible: 'internal' (team only, default) or 'public' (posted to the status page). |
Parameters from the server's own tool schema.
Why add_incident_note is rated Medium
An AI agent can call add_incident_note faster than any human can review: one bad instruction and it creates or modifies resources in OneUptime by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs add_incident_note safely
PolicyLayer is an MCP gateway: it sits between your AI agents and OneUptime, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_incident_note, this is the rule to start with:
add_incident_note 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 OneUptime, apply this rule, and every add_incident_note call is checked against it from then on.
Questions about add_incident_note
Add a note to an incident. Internal notes are visible to your team only; public notes are posted to the status page for subscribers/customers. Markdown is supported. It is categorised as a Write tool in the OneUptime MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
add_incident_note accepts 3 parameters: note, incidentId, visibility. Required: note, incidentId. The full parameter table on this page comes from the server's own tool schema.
Register the OneUptime MCP server in PolicyLayer and add a rule for add_incident_note: 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 OneUptime. Nothing to install.
add_incident_note 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_incident_note 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_incident_note. 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_incident_note is provided by the OneUptime MCP server (https://oneuptime.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on OneUptime, and thousands of servers like it.
This server
Across the catalogue