create_incident_state

SERVEROneUptime SOURCEhttps://oneuptime.com/mcp

Medium RISK CLASS

Category Write

Parameters 92 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What create_incident_state does on OneUptime

AI agents use create_incident_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
`name`	string	Yes	Any friendly name of this object.
`color`	object	Yes	Color of this resource in Hex (#32a852 for example).
`order`	integer	—	Where this state sits in the project's list of incident states: 1 is the top. Incidents only ever move down the list, and an incident in a state at or below the
`projectId`	string	—	ID of your OneUptime Project in which this object belongs.
`isArchived`	boolean	—	Archived states stay on the incidents 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 incident?
`isResolvedState`	boolean	—	Is it the resolved state of the incident?
`isAcknowledgedState`	boolean	—	Is it the acknowledged state of the incident?

Parameters from the server's own tool schema.

RISK

Why create_incident_state is rated Medium

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

create_incident_state Rate-limited

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

FAQ

Questions about create_incident_state

What does the create_incident_state tool do? +

Create a new Incident State in OneUptime. Returns the created Incident State object with its ID. Use this to add new Incident States to your project. Note: projectId is inferred from your API key — you do not need to provide it. 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 create_incident_state accept? +

create_incident_state accepts 9 parameters: name, color, order, projectId, isArchived, description, isCreatedState, isResolvedState, isAcknowledgedState. Required: name, color. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_incident_state? +

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

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

Can I rate-limit create_incident_state? +

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

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

create_incident_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

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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