update_scheduled_maintenance_event

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/update-scheduled-maintenance-event.md

WHAT IT DOES

What update_scheduled_maintenance_event does on OneUptime

AI agents use update_scheduled_maintenance_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
`id`	string	Yes	The unique identifier (UUID) of the Scheduled Maintenance Event to update. Required. Use list_scheduled_maintenance_events to find IDs.
`hosts`	array	—	List of hosts affected by this event.
`title`	string	—	Title of this scheduled event.
`endsAt`	object	—	When does this event end?
`labels`	array	—	Relation to Labels Array where this object is categorized in.
`monitors`	array	—	List of monitors attached to this event.
`services`	array	—	List of services affected by this event.
`startsAt`	object	—	When does this event start?
`iotFleets`	array	—	List of IoT fleets affected by this event.
`description`	string	—	Description of this scheduled event that will show up on Status Page. This is in markdown.
`dockerHosts`	array	—	List of Docker hosts affected by this event.
`podmanHosts`	array	—	List of Podman hosts affected by this event.

Parameters from the server's own tool schema.

RISK

Why update_scheduled_maintenance_event is rated Medium

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

Risk signalsHigh parameter count (45 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_scheduled_maintenance_event Rate-limited

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

FAQ

Questions about update_scheduled_maintenance_event

What does the update_scheduled_maintenance_event tool do? +

Update an existing Scheduled Maintenance Event in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_scheduled_maintenance_event 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_scheduled_maintenance_event accept? +

update_scheduled_maintenance_event accepts 12 parameters: id, hosts, title, endsAt, labels, monitors, services, startsAt, iotFleets, description, dockerHosts, podmanHosts. 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_scheduled_maintenance_event? +

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

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

Can I rate-limit update_scheduled_maintenance_event? +

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

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

update_scheduled_maintenance_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

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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