AI agents call flowise_get_flow to retrieve information from Flowise without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name strongly suggests a query/retrieval operation for retrieving a specific flow object from a Flowise instance. No mutation or execution of the flow is implied. Confidence is reduced slightly due to empty description, but the naming convention and context of sibling tools provide sufficient evidence for Read classification with low severity, as it only retrieves data with no blast radius for misuse.
From the tool's definition Tool name 'flowise_get_flow' suggests retrieval of flow data. The description is empty, but the pattern of sibling tools shows flowise_list_flows and flowise_get_flow are distinct read operations, while flowise_create_flow, flowise_delete_flow, and…
Attacks that exploit this kind of access
flowise_get_flow. It is categorised as a Read tool in the Flowise MCP Server, which means it retrieves data without modifying state.
Register the Flowise MCP server in PolicyLayer and add a rule for flowise_get_flow: 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 Flowise. Nothing to install.
flowise_get_flow 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 flowise_get_flow 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 flowise_get_flow. 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.
flowise_get_flow is provided by the Flowise MCP server (julidir/flowise-mcp). 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 →