generate_flow_paths · Sablier MCP Server MCP: Risk & Policy

WHAT IT DOES

What generate_flow_paths does on Sablier MCP Server

AI agents invoke generate_flow_paths to trigger actions in Sablier MCP Server. 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 generate_flow_paths needs a policy

Based on the server description mentioning generating synthetic market paths and the tool name, this likely executes a computation to produce synthetic data. Empty description lowers confidence. Not clearly financial, destructive, or write — most likely Execute as it triggers an external computation/generation process.

From the tool's definition Tool name 'generate_flow_paths' and server context mentions 'generate synthetic market paths'; description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_flow_paths Rate-limited

generate_flow_paths 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": {
    "generate_flow_paths": {
      "limits": [
        {
          "counter": "generate_flow_paths_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 Sablier MCP Server, so you can run agents against it safely.

FAQ

Questions about generate_flow_paths

What does the generate_flow_paths tool do? +

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

How do I enforce a policy on generate_flow_paths? +

Register the Sablier MCP Server MCP server in PolicyLayer and add a rule for generate_flow_paths: 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 Sablier MCP Server. Nothing to install.

What risk level is generate_flow_paths? +

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

Can I rate-limit generate_flow_paths? +

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

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

generate_flow_paths is provided by the Sablier MCP Server MCP server (sablier-ai/sablier-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.