AI agents call list_workflow_schedules to retrieve information from Lens without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
workflow_id | string | Yes | Workflow UUID |
Parameters from the server's own tool schema.
This tool queries and retrieves information about existing workflow schedules without creating, modifying, deleting, or executing anything. It is a read-only operation with minimal blast radius if misused—an agent would only gain visibility into workflow schedule configuration.
From the tool's definition Tool name 'list_workflow_schedules' and description 'List scheduled runs configured for a workflow' indicate a retrieval operation with no modification or execution of workflows.
Attacks that exploit this kind of access
List scheduled runs configured for a workflow. It is categorised as a Read tool in the Lens MCP Server, which means it retrieves data without modifying state.
list_workflow_schedules accepts 1 parameter: workflow_id. Required: 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 list_workflow_schedules: 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.
list_workflow_schedules is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_workflow_schedules 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 list_workflow_schedules. 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.
list_workflow_schedules 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 →