list_flow_scenarios
AI agents call list_flow_scenarios to retrieve information from Sablier MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_' prefix is characteristic of Read tools that enumerate or retrieve data. The empty description reduces confidence slightly, but the naming pattern and server's analytical purpose (analyze, stress-test, scan) indicate this tool queries existing scenario data rather than modifying, executing operations, or moving funds. Financial data retrieval without side effects is Read category with low severity.
From the tool's definition Tool name 'list_flow_scenarios' contains the verb 'list', which is a classic Read operation. The sibling tools and server context indicate this is a financial analysis platform, and listing scenarios is a non-destructive retrieval operation.
Attacks that exploit this kind of access
list_flow_scenarios. It is categorised as a Read tool in the Sablier MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sablier MCP Server MCP server in PolicyLayer and add a rule for list_flow_scenarios: 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.
list_flow_scenarios is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_flow_scenarios 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.
Set action: deny in the PolicyLayer policy for list_flow_scenarios. 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.
list_flow_scenarios 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →