vibecontrols_actions_schedule

Create a scheduled job for a Vibe Action via the scheduler service.

SERVERVibecontrols SOURCE@vibecontrols/mcp

Medium RISK CLASS

Category Write

Parameters 102 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/vibecontrols-mcp/vibecontrols-actions-schedule.md

WHAT IT DOES

What vibecontrols_actions_schedule does on Vibecontrols

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

Parameter	Type	Required	Description
`name`	string	—	Name for the scheduled job
`endDate`	string	—	Schedule end date (ISO)
`actionId`	string	Yes	Action ID to schedule
`interval`	number	—	Interval value (for FIXED_INTERVAL)
`timezone`	string	—	Timezone (default UTC)
`startDate`	string	—	Schedule start date (ISO)
`scheduledAt`	string	—	ISO date for ONE_TIME schedule
`intervalUnit`	string	—	Interval unit (MINUTES, HOURS, DAYS)
`scheduleType`	string	Yes	Schedule type (CRON, ONE_TIME, FIXED_INTERVAL)
`cronExpression`	string	—	Cron expression (for CRON type)

Parameters from the server's own tool schema.

RISK

Why vibecontrols_actions_schedule is rated Medium

An AI agent can call vibecontrols_actions_schedule faster than any human can review: one bad instruction and it creates or modifies resources in Vibecontrols by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vibecontrols_actions_schedule safely

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

vibecontrols_actions_schedule Rate-limited

vibecontrols_actions_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": {
    "vibecontrols_actions_schedule": {
      "limits": [
        {
          "counter": "vibecontrols_actions_schedule_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vibecontrols, apply this rule, and every vibecontrols_actions_schedule call is checked against it from then on.

FAQ

Questions about vibecontrols_actions_schedule

What does the vibecontrols_actions_schedule tool do? +

Create a scheduled job for a Vibe Action via the scheduler service. It is categorised as a Write tool in the Vibecontrols MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does vibecontrols_actions_schedule accept? +

vibecontrols_actions_schedule accepts 10 parameters: name, endDate, actionId, interval, timezone, startDate, scheduledAt, intervalUnit, scheduleType, cronExpression. Required: actionId, scheduleType. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on vibecontrols_actions_schedule? +

Register the Vibecontrols MCP server in PolicyLayer and add a rule for vibecontrols_actions_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 Vibecontrols. Nothing to install.

What risk level is vibecontrols_actions_schedule? +

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

Can I rate-limit vibecontrols_actions_schedule? +

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

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

vibecontrols_actions_schedule is provided by the Vibecontrols MCP server (@vibecontrols/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vibecontrols, and thousands of servers like it.

This server

All 672 Vibecontrols tools →

Across the catalogue

aiva_subscription_actions on AIVA MCP Server →sms_schedule on Twilio SMS MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →