create_monitor_status_event

SERVEROneUptime SOURCEhttps://oneuptime.com/mcp

Medium RISK CLASS

Category Write

Parameters 62 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-monitor-status-event.md

WHAT IT DOES

What create_monitor_status_event does on OneUptime

AI agents use create_monitor_status_event 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
`endsAt`	object	—	When did this status change end?
`startsAt`	object	—	When did this status change?
`monitorId`	string	Yes	Relation to Monitor ID Resource in which this object belongs.
`projectId`	string	—	ID of your OneUptime Project in which this object belongs.
`rootCause`	string	—	What is the root cause of this status change?
`monitorStatusId`	string	Yes	Relation to Monitor Status ID Resource in which this object belongs.

Parameters from the server's own tool schema.

RISK

Why create_monitor_status_event is rated Medium

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

create_monitor_status_event Rate-limited

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

FAQ

Questions about create_monitor_status_event

What does the create_monitor_status_event tool do? +

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

create_monitor_status_event accepts 6 parameters: endsAt, startsAt, monitorId, projectId, rootCause, monitorStatusId. Required: monitorId, monitorStatusId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_monitor_status_event? +

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

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

Can I rate-limit create_monitor_status_event? +

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

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

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