get_scheduled_maintenance_event
Retrieve a single Scheduled Maintenance Event by its unique ID from OneUptime. Use list_scheduled_maintenance_events first if you need to find the ID.
This record as markdown: /tools/com-oneuptime-mcp/get-scheduled-maintenance-event.md
What get_scheduled_maintenance_event does on OneUptime
AI agents call get_scheduled_maintenance_event 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | The unique identifier (UUID) of the Scheduled Maintenance Event to retrieve. Example: "550e8400-e29b-41d4-a716-446655440000" |
select | array | — | Optional: field names to return for each Scheduled Maintenance Event (e.g. ["_id", "name"]). Omit to get all readable fields. Large fields excluded by default ( |
Parameters from the server's own tool schema.
Why get_scheduled_maintenance_event is rated Low
Even though get_scheduled_maintenance_event 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.
Attacks that exploit this kind of access
The rule that runs get_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 get_scheduled_maintenance_event, this is the rule to start with:
get_scheduled_maintenance_event is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect OneUptime, apply this rule, and every get_scheduled_maintenance_event call is checked against it from then on.
Questions about get_scheduled_maintenance_event
Retrieve a single Scheduled Maintenance Event by its unique ID from OneUptime. Use list_scheduled_maintenance_events first if you need to find the ID. It is categorised as a Read tool in the OneUptime MCP Server, which means it retrieves data without modifying state.
get_scheduled_maintenance_event accepts 2 parameters: id, select. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the OneUptime MCP server in PolicyLayer and add a rule for get_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.
get_scheduled_maintenance_event is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
More on OneUptime, and thousands of servers like it.
This server
Across the catalogue