AI agents use update_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 | — | Enable or disable schedule |
cron_expr | string | — | Cron expression with 5 fields |
input_data | object | — | JSON object used as workflow input on each scheduled run |
schedule_id | string | Yes | Schedule UUID |
workflow_id | string | Yes | Workflow UUID |
Parameters from the server's own tool schema.
The tool modifies existing workflow schedule configurations rather than creating new ones (Write rather than Execute). The changes are reversible and do not permanently delete data (not Destructive). The impact is limited to scheduling metadata rather than triggering immediate execution or financial operations.
From the tool's definition Tool description explicitly states 'Update a workflow schedule' with capabilities to modify 'enable/disable, cron expression, input payload' — this is data modification that is reversible (schedules can be re-updated).
Attacks that exploit this kind of access
Update a workflow schedule (enable/disable, cron expression, input payload). Timezone is fixed server-side. 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.
update_workflow_schedule accepts 5 parameters: enabled, cron_expr, input_data, schedule_id, workflow_id. Required: schedule_id, 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 update_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.
update_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 update_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 update_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.
update_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 →