update_execute_schedule · Morpheus MCP Server MCP

WHAT IT DOES

What update_execute_schedule does on Morpheus MCP Server

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

This tool modifies execution schedules reversibly (schedules can be re-updated to previous values). It does not execute workflows (that would be Execute category), nor does it delete schedules (that would be Destructive).

From the tool's definition Tool description states 'Update an execution schedule — rename, change cron expression, or enable/disable.' The verb 'update' and operations like 'rename,' 'change cron expression,' and 'enable/disable' indicate modification of existing configuration objects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_execute_schedule Rate-limited

update_execute_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_execute_schedule": {
      "limits": [
        {
          "counter": "update_execute_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_execute_schedule

What does the update_execute_schedule tool do? +

Update an execution schedule — rename, change cron expression, 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_execute_schedule? +

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

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

Can I rate-limit update_execute_schedule? +

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

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

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