create_incident

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/create-incident.md

WHAT IT DOES

What create_incident does on OneUptime

AI agents use create_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
`hosts`	array	—	List of hosts affected by this incident.
`title`	string	Yes	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
`projectId`	string	—	ID of your OneUptime Project in which this object belongs.
`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 create_incident is rated Medium

An AI agent can call create_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 (69 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

create_incident Rate-limited

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

FAQ

Questions about create_incident

What does the create_incident tool do? +

Create a new Incident in OneUptime. Returns the created Incident object with its ID. Use this to add new Incidents 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 accept? +

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

How do I enforce a policy on create_incident? +

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

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

Can I rate-limit create_incident? +

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

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

create_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

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 →