# get_public_status_page_scheduled_maintenance

Get scheduled maintenance events from a public status page. This tool does NOT require an API key and works with public status pages. Status page owners can disable MCP access for their status page. If disabled, this tool returns an error and the data must be read from the status page website or its RSS feed instead. USAGE: - By domain: statusPageIdOrDomain = "status.company.com" - By ID: statusPageIdOrDomain = "550e8400-e29b-41d4-a716-446655440000" RETURNS: - List of scheduled maintenance events (upcoming and ongoing) - Maintenance details (title, description, scheduled times) - Maintenance timeline and state changes - Public notes/updates for each maintenance event

Agent View of the PolicyLayer registry record for `get_public_status_page_scheduled_maintenance`. HTML page: https://policylayer.com/tools/com-oneuptime-mcp/get-public-status-page-scheduled-maintenance

## Facts

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

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `statusPageIdOrDomain` | string | yes | The status page ID (UUID) or domain name (e.g., 'status.company.com') |
| `scheduledMaintenanceId` | string | no | Optional: Specific scheduled maintenance ID to fetch details for |

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": "get_public_status_page_scheduled_maintenance",
    "arguments": {
      "statusPageIdOrDomain": "<statusPageIdOrDomain>"
    }
  }
}
```

## Why get_public_status_page_scheduled_maintenance is rated Low

Even though get_public_status_page_scheduled_maintenance only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call get_public_status_page_scheduled_maintenance to retrieve information from OneUptime without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_public_status_page_scheduled_maintenance": {}
  }
}
```

## 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