check_scenario_probability
AI agents call check_scenario_probability 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.
Despite the empty description reducing confidence, the tool name strongly suggests a query or computation operation that retrieves or calculates scenario probability data without modifying state. The broader server context (portfolio analysis, stress-testing, synthetic path generation, SEC scanning) supports this being an analytical query rather than a write, execute, or destructive operation.
From the tool's definition Tool name 'check_scenario_probability' suggests querying or calculating probability metrics for scenarios. The server context indicates analysis and stress-testing capabilities.
Attacks that exploit this kind of access
check_scenario_probability. 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 check_scenario_probability: 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.
check_scenario_probability 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 check_scenario_probability 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 check_scenario_probability. 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.
check_scenario_probability 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 →