find_flow

What find_flow does on Kestra Python MCP Server

AI agents call find_flow 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 find_flow is rated Low

Based on the tool name 'find_flow' and its position among sibling tools that explicitly perform mutations and deletions, this tool most likely retrieves or searches for flow definitions without modifying state. Confidence is reduced slightly due to the empty description, but the naming strongly indicates a read operation typical of workflow query interfaces.

From the tool's definition Tool name 'find_flow' suggests a search/query operation to locate workflow definitions. The empty description prevents full certainty, but naming convention and context within a workflow management system indicate a retrieval function.

The rule that runs find_flow 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 find_flow, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_flow": {}
  }
}

Questions about find_flow