Create a recurring schedule for a workflow using cron (5 fields). Timezone is fixed server-side (default America/Sao_Paulo). Optional input_data is passed to each run (same object shape as execute workflow body field input).
AI agents use create_workflow_schedule to create or update resources in Lens — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lens environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
enabled | boolean | — | Whether schedule starts enabled |
cron_expr | string | Yes | Cron expression with 5 fields (minute hour day month weekday) |
input_data | object | — | JSON object used as workflow input on each scheduled run (maps to execute `input`) |
workflow_id | string | Yes | Workflow UUID |
Parameters from the server's own tool schema.
This tool creates (not reads, executes, or deletes) a new workflow schedule object. While it triggers recurring executions, the primary action is establishing a configuration record—a reversible write operation. The severity is medium because misconfiguration could cause unintended recurring workflow executions with side effects, but the tool itself is not destructive or financial.
From the tool's definition Tool name 'create_workflow_schedule' and description 'Create a recurring schedule' indicate data creation. The tool sets up a persistent, recurring configuration that modifies the system state by establishing a new scheduled task.
Attacks that exploit this kind of access
Create a recurring schedule for a workflow using cron (5 fields). Timezone is fixed server-side (default America/Sao_Paulo). Optional input_data is passed to each run (same object shape as execute workflow body field input). It is categorised as a Write tool in the Lens MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_workflow_schedule accepts 4 parameters: enabled, cron_expr, input_data, workflow_id. Required: cron_expr, workflow_id. The full parameter table on this page comes from the server's own tool schema.
Register the Lens MCP server in PolicyLayer and add a rule for create_workflow_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 Lens. Nothing to install.
create_workflow_schedule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_workflow_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.
Set action: deny in the PolicyLayer policy for create_workflow_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.
create_workflow_schedule is provided by the Lens MCP server (lens-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →