update_power_schedule · Morpheus MCP Server MCP

WHAT IT DOES

What update_power_schedule does on Morpheus MCP Server

AI agents use update_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 update_power_schedule needs a policy

This tool modifies power schedule properties in a reversible manner. Renaming and toggling enable/disable states are Write operations—they change data/configuration but can be undone by reverting to previous values. While it could impact running instances if disabling schedules (enabling/disabling power schedules could cause unintended VM shutdowns), the operation itself is not destructive or irreversible.

From the tool's definition Tool description: 'Update a power schedule — rename or enable/disable.' This modifies existing power schedule configuration (rename, enable/disable state), which are reversible changes to infrastructure settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_power_schedule Rate-limited

update_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": {
    "update_power_schedule": {
      "limits": [
        {
          "counter": "update_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 update_power_schedule

What does the update_power_schedule tool do? +

Update a power schedule — rename or enable/disable. 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 update_power_schedule? +

Register the Morpheus MCP Server MCP server in PolicyLayer and add a rule for update_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 update_power_schedule? +

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

Can I rate-limit update_power_schedule? +

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

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

update_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.