flowise_predict · Flowise MCP: Risk & Policy

WHAT IT DOES

What flowise_predict does on Flowise

AI agents invoke flowise_predict to trigger actions in Flowise. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why flowise_predict needs a policy

In Flowise, 'predict' typically means sending an input to a chatflow or pipeline and executing it, which triggers external operations (LLM calls, API calls, agent runs). This falls under Execute as it runs external operations. The empty description lowers confidence, but the name and Flowise context strongly imply execution of a flow/prediction pipeline.

From the tool's definition Tool name 'flowise_predict' suggests triggering a prediction/inference operation in a Flowise flow; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

flowise_predict Rate-limited

flowise_predict stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_predict": {
      "limits": [
        {
          "counter": "flowise_predict_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_predict

What does the flowise_predict tool do? +

flowise_predict. It is categorised as a Execute tool in the Flowise MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on flowise_predict? +

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

flowise_predict is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit flowise_predict? +

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

Set action: deny in the PolicyLayer policy for flowise_predict. 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_predict? +

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