# create_scheduled_maintenance_state_timeline

Create a new Scheduled Maintenance State Timeline in OneUptime. Returns the created Scheduled Maintenance State Timeline object with its ID. Use this to add new Scheduled Maintenance State Timelines to your project. Note: projectId is inferred from your API key — you do not need to provide it.

Agent View of the PolicyLayer registry record for `create_scheduled_maintenance_state_timeline`. HTML page: https://policylayer.com/tools/com-oneuptime-mcp/create-scheduled-maintenance-state-timeline

## Facts

- Tool: `create_scheduled_maintenance_state_timeline`
- Server: OneUptime (`https://oneuptime.com/mcp`) — https://policylayer.com/tools/com-oneuptime-mcp.md
- Homepage: https://github.com/OneUptime/oneuptime
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 6 (2 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `endsAt` | object | no | When did this status change end? |
| `startsAt` | object | no | When did this status change? Correct this when the recorded time is wrong - every measurement derived from this timeline is recomputed from the corrected value. |
| `projectId` | string | no | ID of your OneUptime Project in which this object belongs. |
| `scheduledMaintenanceId` | string | yes | ID of Scheduled Maintenance this resource belongs to. |
| `scheduledMaintenanceStateId` | string | yes | Scheduled Maintenance State ID. Which state does this event belongs to? |
| `shouldStatusPageSubscribersBeNotified` | boolean | no | Should subscribers be notified about this state change? |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "create_scheduled_maintenance_state_timeline",
    "arguments": {
      "scheduledMaintenanceId": "<scheduledMaintenanceId>",
      "scheduledMaintenanceStateId": "<scheduledMaintenanceStateId>"
    }
  }
}
```

## Why create_scheduled_maintenance_state_timeline is rated Medium

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

## Use case

AI agents use create_scheduled_maintenance_state_timeline 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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches OneUptime:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_scheduled_maintenance_state_timeline": {
      "limits": [
        {
          "counter": "create_scheduled_maintenance_state_timeline_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on OneUptime (222)

- `delete_alert` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-alert.md
- `delete_alert_internal_note` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-alert-internal-note.md
- `delete_alert_severity` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-alert-severity.md
- `delete_alert_state` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-alert-state.md
- `delete_alert_state_timeline` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-alert-state-timeline.md
- `delete_incident` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident.md
- `delete_incident_alert` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident-alert.md
- `delete_incident_internal_note` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident-internal-note.md
- `delete_incident_public_note` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident-public-note.md
- `delete_incident_severity` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident-severity.md
- `delete_incident_state` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident-state.md
- `delete_incident_state_timeline` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-incident-state-timeline.md
- `delete_label` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-label.md
- `delete_monitor` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-monitor.md
- `delete_monitor_status` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-monitor-status.md
- `delete_monitor_status_event` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-monitor-status-event.md
- `delete_on_call_policy` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-on-call-policy.md
- `delete_postmortem_status` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-postmortem-status.md
- `delete_scheduled_maintenance_event` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-scheduled-maintenance-event.md
- `delete_scheduled_maintenance_state` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-scheduled-maintenance-state.md
- `delete_scheduled_maintenance_state_timeline` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-scheduled-maintenance-state-timeline.md
- `delete_security_case` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-case.md
- `delete_security_case_evidence` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-case-evidence.md
- `delete_security_case_note` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-case-note.md
- `delete_security_case_priority` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-case-priority.md
- `delete_security_case_status` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-case-status.md
- `delete_security_case_task` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-case-task.md
- `delete_security_detection` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-detection.md
- `delete_security_playbook` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-security-playbook.md
- `delete_status_page` — Destructive — https://policylayer.com/tools/com-oneuptime-mcp/delete-status-page.md
- …and 192 more: https://policylayer.com/tools/com-oneuptime-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-oneuptime-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-oneuptime-mcp