flowise_create_flow · Flowise MCP: Risk & Policy

WHAT IT DOES

What flowise_create_flow does on Flowise

AI agents use flowise_create_flow to create or update resources in Flowise — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Flowise environment.

WHY IT NEEDS A POLICY

Why flowise_create_flow needs a policy

Creating a flow is a reversible write operation that modifies the state of the Flowise instance by adding new flow definitions. While the tool does not delete or execute arbitrary code directly, it creates persistent configuration objects that could potentially affect downstream automation or analysis.

From the tool's definition Tool name is 'flowise_create_flow' which indicates creation of a new flow artifact. Description is empty, so classification relies on the name and context of sibling tools (flowise_delete_flow, flowise_get_flow, flowise_list_flows) which confirm this is a…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

flowise_create_flow Rate-limited

flowise_create_flow stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "flowise_create_flow": {
      "limits": [
        {
          "counter": "flowise_create_flow_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Flowise, so you can run agents against it safely.

FAQ

Questions about flowise_create_flow

What does the flowise_create_flow tool do? +

flowise_create_flow. It is categorised as a Write tool in the Flowise MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on flowise_create_flow? +

Register the Flowise MCP server in PolicyLayer and add a rule for flowise_create_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.

What risk level is flowise_create_flow? +

flowise_create_flow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit flowise_create_flow? +

Yes. Add a rate_limit block to the flowise_create_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.

How do I block flowise_create_flow completely? +

Set action: deny in the PolicyLayer policy for flowise_create_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.

What MCP server provides flowise_create_flow? +

flowise_create_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.