List past beta computation runs for a Moment model group. Each entry is a compute_betas invocation with its simulation_batch_id, date, and status. Use this to find older simulation_batch_ids for compute_returns. NOT for Flow models — use list_flow_scenarios for those.
AI agents call list_simulations 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.
This tool retrieves historical simulation metadata for informational purposes only. It has no side effects, does not execute code or trigger operations, does not modify data, and does not involve financial transactions. The blast radius of misuse is minimal—an agent could only access records of past computations that have already been completed.
From the tool's definition Tool description explicitly states it 'List[s] past beta computation runs' and retrieves entries with 'simulation_batch_id, date, and status'.
Attacks that exploit this kind of access
List past beta computation runs for a Moment model group. Each entry is a compute_betas invocation with its simulation_batch_id, date, and status. Use this to find older simulation_batch_ids for compute_returns. NOT for Flow models — use list_flow_scenarios for those. 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_simulations: 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_simulations 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_simulations 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_simulations. 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_simulations 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 →