ops_schedule_maintenance · Ops MCP: Risk & Policy

WHAT IT DOES

What ops_schedule_maintenance does on Ops

AI agents use ops_schedule_maintenance to create or update resources in Ops — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ops environment.

WHY IT NEEDS A POLICY

Why ops_schedule_maintenance needs a policy

This tool creates maintenance window records on two external monitoring/status systems. While creation is reversible (maintenance windows can be ended), it materially modifies the operational state visible to customers and stakeholders—downtime windows are announced and tracked. The blast radius is high because an AI agent scheduling unintended maintenance could disrupt service visibility and customer communications.

From the tool's definition Tool description states: 'Create a maintenance window on BOTH Statuspage and Uptime Kuma'. The verb 'Create' indicates creation of new data (maintenance window records) that is reversible by ending/deleting the maintenance window.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ops_schedule_maintenance Rate-limited

ops_schedule_maintenance 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": {
    "ops_schedule_maintenance": {
      "limits": [
        {
          "counter": "ops_schedule_maintenance_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ops, so you can run agents against it safely.

FAQ

Questions about ops_schedule_maintenance

What does the ops_schedule_maintenance tool do? +

Create a maintenance window on BOTH Statuspage and Uptime Kuma. It is categorised as a Write tool in the Ops MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ops_schedule_maintenance? +

Register the Ops MCP server in PolicyLayer and add a rule for ops_schedule_maintenance: 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 Ops. Nothing to install.

What risk level is ops_schedule_maintenance? +

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

Can I rate-limit ops_schedule_maintenance? +

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

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

ops_schedule_maintenance is provided by the Ops MCP server (sydney-robotics-academy/ops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.