create_execute_schedule · Morpheus MCP Server MCP

WHAT IT DOES

What create_execute_schedule does on Morpheus MCP Server

AI agents invoke create_execute_schedule to trigger actions in Morpheus MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why create_execute_schedule needs a policy

In the context of an HPE Morpheus infrastructure management server that explicitly supports executing workflows, a 'create_execute_schedule' tool most likely creates a schedule that triggers automated execution of tasks or workflows. The 'execute' component places this above Write. Empty description reduces confidence, but sibling tools and server context support this interpretation.

From the tool's definition Tool name 'create_execute_schedule' — 'execute' strongly implies scheduling execution of workflows or operations; description is empty and uninformative, lowering confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_execute_schedule Rate-limited

create_execute_schedule stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_execute_schedule": {
      "limits": [
        {
          "counter": "create_execute_schedule_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_execute_schedule

What does the create_execute_schedule tool do? +

create_execute_schedule. It is categorised as a Execute tool in the Morpheus MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on create_execute_schedule? +

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

create_execute_schedule is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit create_execute_schedule? +

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

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

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