update_alert_state

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

SERVEROneUptime SOURCEhttps://oneuptime.com/mcp

Medium RISK CLASS

Category Write

Parameters 91 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-alert-state.md

WHAT IT DOES

What update_alert_state does on OneUptime

AI agents use update_alert_state 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 Alert State to update. Required. Use list_alert_states to find IDs.
`name`	string	—	Any friendly name of this object.
`color`	object	—	Color of this resource in Hex (#32a852 for example).
`order`	integer	—	Where this state sits in the project's list of alert states: 1 is the top. Alerts only ever move down the list, and an alert in a state at or below the acknowle
`isArchived`	boolean	—	Archived states stay on the alerts and episodes that are in them, but can't be picked again. The created, acknowledged and resolved states can't be archived.
`description`	string	—	Friendly description that will help you remember.
`isCreatedState`	boolean	—	Is it the created state of the alert?
`isResolvedState`	boolean	—	Is it the resolved state of the alert?
`isAcknowledgedState`	boolean	—	Is it the acknowledged state of the alert?

Parameters from the server's own tool schema.

RISK

Why update_alert_state is rated Medium

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

RECOMMENDED RULE

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

update_alert_state Rate-limited

update_alert_state 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_alert_state": {
      "limits": [
        {
          "counter": "update_alert_state_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_alert_state call is checked against it from then on.

FAQ

Questions about update_alert_state

What does the update_alert_state tool do? +

Update an existing Alert State in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_alert_state 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_alert_state accept? +

update_alert_state accepts 9 parameters: id, name, color, order, isArchived, description, isCreatedState, isResolvedState, isAcknowledgedState. 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_alert_state? +

Register the OneUptime MCP server in PolicyLayer and add a rule for update_alert_state: 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_alert_state? +

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

Can I rate-limit update_alert_state? +

Yes. Add a rate_limit block to the update_alert_state 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_alert_state completely? +

Set action: deny in the PolicyLayer policy for update_alert_state. 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_alert_state? +

update_alert_state 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 →