Delete a workflow schedule permanently.
AI agents call delete_workflow_schedule to permanently remove resources in Lens — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
schedule_id | string | Yes | Schedule UUID |
workflow_id | string | Yes | Workflow UUID |
Parameters from the server's own tool schema.
This tool irreversibly deletes a workflow schedule, which cannot be undone. Even though it affects configuration rather than user data, permanent deletion of automation schedules constitutes a destructive action with meaningful blast radius—an agent could disable critical workflows. This is more severe than Write (reversible modifications) and maps clearly to the Destructive category.
From the tool's definition Tool name includes 'delete' and description states 'Delete a workflow schedule permanently.' The word 'permanently' indicates an irreversible operation.
Attacks that exploit this kind of access
Delete a workflow schedule permanently. It is categorised as a Destructive tool in the Lens MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_workflow_schedule accepts 2 parameters: 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 delete_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.
delete_workflow_schedule is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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 →