AI agents call list_workflows 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 |
|---|---|---|---|
search | string | — | Filter workflows by name |
include_schedules | boolean | — | Include schedule count / next run for each workflow |
Parameters from the server's own tool schema.
This tool queries and retrieves workflow data without creating, modifying, deleting, or executing anything. The optional search filter and schedule summary inclusion remain read-only operations. No side effects or state changes occur.
From the tool's definition Tool description states 'List workflows' and 'shows schedule summary' — core retrieval operations with no modification or execution. Verb 'list' is explicitly a Read-category action per schema guidance.
Attacks that exploit this kind of access
List workflows from the Lens API. Optionally filter by name with 'search'. If include_schedules=true, also shows schedule summary for each workflow. It is categorised as a Read tool in the Lens MCP Server, which means it retrieves data without modifying state.
list_workflows accepts 2 parameters: search, include_schedules. 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_workflows: 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_workflows 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_workflows 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_workflows. 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_workflows 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 →