detach_power_schedule_instances · Morpheus MCP Server MCP

WHAT IT DOES

What detach_power_schedule_instances does on Morpheus MCP Server

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

This tool modifies cloud infrastructure configuration by detaching instances from automated power control. While reversible (instances can be re-attached), it alters infrastructure state and could affect operational continuity if instances lose intended power management. It is not destructive (no deletion), not financial, and not execute (no arbitrary code).

From the tool's definition 'Remove instances from a power schedule' - modifies the association/binding of instances to power schedules, changing their power management configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

detach_power_schedule_instances Rate-limited

detach_power_schedule_instances 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": {
    "detach_power_schedule_instances": {
      "limits": [
        {
          "counter": "detach_power_schedule_instances_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 detach_power_schedule_instances

What does the detach_power_schedule_instances tool do? +

Remove instances from a power schedule (they will no longer be controlled by it). 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 detach_power_schedule_instances? +

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

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

Can I rate-limit detach_power_schedule_instances? +

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

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

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