Retrieve all flows in a given namespace.
AI agents call list_flows_in_namespace to retrieve information from Kestra Python MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/lists data (flows) from a namespace without creating, modifying, deleting, or executing anything. It is a pure read operation with minimal blast radius if misused by an AI agent—at worst, it exposes workflow metadata that may already be accessible to authenticated users.
From the tool's definition Tool name 'list_flows_in_namespace' and description 'Retrieve all flows in a given namespace' indicate a read-only query operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_flows_in_namespace gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kestra Python MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_flows_in_namespace:
{
"version": "1",
"default": "deny",
"tools": {
"list_flows_in_namespace": {}
}
}list_flows_in_namespace is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve all flows in a given namespace. 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_in_namespace: 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_in_namespace 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_in_namespace 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_in_namespace. 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_in_namespace 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.
Start from Kestra Python MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 Kestra Python MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.