flowise_update_flow · Flowise MCP: Risk & Policy

WHAT IT DOES

What flowise_update_flow does on Flowise

AI agents use flowise_update_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_update_flow needs a policy

The tool modifies an existing flow in Flowise, which is a reversible change (flows can be updated again or restored). This is Write category rather than Execute because it changes configuration/data rather than triggering code execution. The empty description prevents higher confidence, but the name and server context (flow management) strongly indicate a data modification action.

From the tool's definition Tool name 'flowise_update_flow' indicates modification of flow data. The sibling tools on this server include flowise_create_flow, flowise_delete_flow, and flowise_get_flow, establishing a pattern where flows are managed entities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

flowise_update_flow Rate-limited

flowise_update_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_update_flow": {
      "limits": [
        {
          "counter": "flowise_update_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_update_flow

What does the flowise_update_flow tool do? +

flowise_update_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_update_flow? +

Register the Flowise MCP server in PolicyLayer and add a rule for flowise_update_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_update_flow? +

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

Can I rate-limit flowise_update_flow? +

Yes. Add a rate_limit block to the flowise_update_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_update_flow completely? +

Set action: deny in the PolicyLayer policy for flowise_update_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_update_flow? +

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