set_schedule

What set_schedule does on Vultr MCP

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

Why set_schedule is rated Medium

Setting a schedule modifies workflow execution parameters but is reversible (can be unset, updated, or deleted via delete_schedule). This is a Write operation rather than Execute because it configures automation rather than directly triggering external actions. Medium severity reflects potential business impact if schedules are misconfigured, but the change is not destructive or financial.

From the tool's definition Tool name 'set_schedule' indicates creation or modification of scheduling configuration. The empty description limits certainty, but naming convention and context within a workflow automation platform (alongside create_workflow, create_trigger) suggests…

The rule that runs set_schedule safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Vultr MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_schedule, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_schedule": {
      "limits": [
        {
          "counter": "set_schedule_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about set_schedule