update_incident_internal_note
Update an existing Incident Internal Note in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_incident_internal_note afterwards to see the updated record.
This record as markdown: /tools/com-oneuptime-mcp/update-incident-internal-note.md
What update_incident_internal_note does on OneUptime
AI agents use update_incident_internal_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 |
|---|---|---|---|
id | string | Yes | The unique identifier (UUID) of the Incident Internal Note to update. Required. Use list_incident_internal_notes to find IDs. |
note | string | — | Notes in markdown. |
postedAt | object | — | Date and time the note belongs to in the timeline: when it was written, or - for a note saved from a Slack or Microsoft Teams message - when that message was po |
attachments | array | — | Files attached to this note. |
Parameters from the server's own tool schema.
Why update_incident_internal_note is rated Medium
An AI agent can call update_incident_internal_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 update_incident_internal_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 update_incident_internal_note, this is the rule to start with:
update_incident_internal_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 update_incident_internal_note call is checked against it from then on.
Questions about update_incident_internal_note
Update an existing Incident Internal Note in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_incident_internal_note afterwards to see the updated record. 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.
update_incident_internal_note accepts 4 parameters: id, note, postedAt, attachments. Required: id. 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 update_incident_internal_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.
update_incident_internal_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 update_incident_internal_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 update_incident_internal_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.
update_incident_internal_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