create_power_schedule · Morpheus MCP Server MCP

WHAT IT DOES

What create_power_schedule does on Morpheus MCP Server

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

WHY IT NEEDS A POLICY

Why create_power_schedule needs a policy

Creating a power schedule is a write operation that generates new infrastructure configuration. It is reversible (can be modified or deleted), but affects operational behavior of VMs. The impact is medium severity because misconfiguration could cause unintended VM shutdowns or startups affecting service availability, but the action itself is not destructive or financially consequential.

From the tool's definition Tool explicitly creates a power schedule artifact that modifies VM automation behavior. Description states 'Create a power schedule to automatically start and stop VMs,' indicating persistent configuration changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_power_schedule Rate-limited

create_power_schedule 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": {
    "create_power_schedule": {
      "limits": [
        {
          "counter": "create_power_schedule_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 Morpheus MCP Server, so you can run agents against it safely.

FAQ

Questions about create_power_schedule

What does the create_power_schedule tool do? +

Create a power schedule to automatically start and stop VMs. It is categorised as a Write tool in the Morpheus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_power_schedule? +

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

What risk level is create_power_schedule? +

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

Can I rate-limit create_power_schedule? +

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

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

create_power_schedule is provided by the Morpheus MCP Server MCP server (nixndme/morpheus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.