update_postmortem_status

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-postmortem-status.md

WHAT IT DOES

What update_postmortem_status does on OneUptime

AI agents use update_postmortem_status 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 Postmortem Status to update. Required. Use list_postmortem_statuses 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 status sits in the project's list of postmortem statuses: 1 is the top. A postmortem in the completed status, or in a status below it, counts as done
`isArchived`	boolean	—	Archived statuses stay on the incidents whose postmortems are in them, but can't be picked again. The not started, draft and completed statuses can't be archive
`description`	string	—	Friendly description that will help you remember.
`isDraftStatus`	boolean	—	Is it the status a postmortem moves to once its note is written? A project has one, and it can't be deleted or archived.
`isCompletedStatus`	boolean	—	Is it the status a postmortem moves to once it is published on a status page? A postmortem in this status, or in one below it, counts as done. A project has one
`isNotStartedStatus`	boolean	—	Is it the status a new incident's postmortem starts in? A project has one, and it can't be deleted or archived.

Parameters from the server's own tool schema.

RISK

Why update_postmortem_status is rated Medium

An AI agent can call update_postmortem_status 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_postmortem_status 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_postmortem_status, this is the rule to start with:

update_postmortem_status Rate-limited

update_postmortem_status 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_postmortem_status": {
      "limits": [
        {
          "counter": "update_postmortem_status_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_postmortem_status call is checked against it from then on.

FAQ

Questions about update_postmortem_status

What does the update_postmortem_status tool do? +

Update an existing Postmortem Status in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_postmortem_status 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_postmortem_status accept? +

update_postmortem_status accepts 9 parameters: id, name, color, order, isArchived, description, isDraftStatus, isCompletedStatus, isNotStartedStatus. 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_postmortem_status? +

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

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

Can I rate-limit update_postmortem_status? +

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

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

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