list_flows_with_triggers
A read tool on the Kestra Python MCP server.
This record as markdown: /tools/kestra-io-mcp-server-python/list-flows-with-triggers.md
What list_flows_with_triggers does on Kestra Python MCP Server
AI agents call list_flows_with_triggers to retrieve information from Kestra Python MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_flows_with_triggers is rated Low
This tool appears to query and retrieve a list of Kestra flows, optionally filtered by trigger status. No description is provided, but the name clearly indicates a listing/read operation. While the description is empty (which lowers confidence slightly from 0.95 to 0.9), the naming convention is unambiguous. Listing flows has no side effects on the system state—it merely retrieves information.
From the tool's definition Tool name contains 'list_flows' which indicates retrieval of flow information without modification. The verb 'list' is typical of Read operations that query/enumerate data.
Attacks that exploit this kind of access
The rule that runs list_flows_with_triggers safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kestra Python MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_flows_with_triggers, this is the rule to start with:
list_flows_with_triggers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Kestra Python MCP Server, apply this rule, and every list_flows_with_triggers call is checked against it from then on.
Questions about list_flows_with_triggers
list_flows_with_triggers is a read tool on the Kestra Python MCP Server MCP server. It is categorised as a Read tool in the Kestra Python MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kestra Python MCP Server MCP server in PolicyLayer and add a rule for list_flows_with_triggers: 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 Kestra Python MCP Server. Nothing to install.
list_flows_with_triggers 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_flows_with_triggers 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_flows_with_triggers. 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_flows_with_triggers is provided by the Kestra Python MCP Server MCP server (kestra-io/mcp-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Kestra Python MCP Server, and thousands of servers like it.
This server
Across the catalogue