update_incident

Update an existing Incident in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_incident afterwards to see the updated record.

SERVEROneUptime SOURCEhttps://oneuptime.com/mcp

Medium RISK CLASS

Category Write

Parameters 121 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-oneuptime-mcp/update-incident.md

WHAT IT DOES

What update_incident does on OneUptime

AI agents use update_incident 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 to update. Required. Use list_incidents to find IDs.
`hosts`	array	—	List of hosts affected by this incident.
`title`	string	—	Title of this incident.
`labels`	array	—	Relation to Labels Array where this object is categorized in.
`monitors`	array	—	List of monitors affected by this incident.
`services`	array	—	List of services affected by this incident.
`iotFleets`	array	—	List of IoT fleets affected by this incident.
`isPrivate`	boolean	—	If true, this incident is only visible to its owners (users in 'owner users' and members of 'owner teams'), project admins, and project owners. Private incident
`rootCause`	string	—	What is the root cause of this incident?
`declaredAt`	object	—	Date and time when this incident was declared.
`description`	string	—	Short description of this incident. This is in markdown and will be visible on the status page.
`dockerHosts`	array	—	List of Docker hosts affected by this incident.

Parameters from the server's own tool schema.

RISK

Why update_incident is rated Medium

An AI agent can call update_incident 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.

Risk signalsHigh parameter count (68 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_incident 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, this is the rule to start with:

update_incident Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_incident": {
      "limits": [
        {
          "counter": "update_incident_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect OneUptime, apply this rule, and every update_incident call is checked against it from then on.

FAQ

Questions about update_incident

What does the update_incident tool do? +

Update an existing Incident in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_incident 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.

What parameters does update_incident accept? +

update_incident accepts 12 parameters: id, hosts, title, labels, monitors, services, iotFleets, isPrivate, rootCause, declaredAt, description, dockerHosts. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_incident? +

Register the OneUptime MCP server in PolicyLayer and add a rule for update_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 OneUptime. Nothing to install.

What risk level is update_incident? +

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

Can I rate-limit update_incident? +

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

How do I block update_incident completely? +

Set action: deny in the PolicyLayer policy for update_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 update_incident? +

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

KEEP EXPLORING

More on OneUptime, and thousands of servers like it.

This server

All 223 OneUptime tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →