test_flow_risk · Sablier MCP Server MCP: Risk & Policy

WHAT IT DOES

What test_flow_risk does on Sablier MCP Server

AI agents invoke test_flow_risk 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 test_flow_risk needs a policy

The description is empty, so classification is based on the tool name and server context. 'test_flow_risk' suggests running a risk analysis or stress test (an execution of a computation/simulation) rather than a simple read. Given sibling tools like 'backtest_rules', 'check_scenario_probability', and 'analyze_derivatives', this tool likely executes a flow risk simulation.

From the tool's definition Tool name 'test_flow_risk' and empty description; server context involves portfolio analysis, stress-testing, and scenario generation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_flow_risk Rate-limited

test_flow_risk 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": {
    "test_flow_risk": {
      "limits": [
        {
          "counter": "test_flow_risk_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 test_flow_risk

What does the test_flow_risk tool do? +

test_flow_risk. 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 test_flow_risk? +

Register the Sablier MCP Server MCP server in PolicyLayer and add a rule for test_flow_risk: 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 test_flow_risk? +

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

Can I rate-limit test_flow_risk? +

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

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

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