create_scenario
AI agents use create_scenario to create or update resources in Sablier MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sablier MCP Server environment.
The name 'create_scenario' strongly suggests a Write operation that creates a new scenario (e.g., a stress-test or market scenario). The description is empty, which lowers confidence. Given the server context of portfolio analysis and stress-testing, this likely creates a scenario configuration reversibly. No evidence of destructive, financial, or execute behavior from the name alone.
From the tool's definition Tool name 'create_scenario' and empty description. Based on naming convention, it likely creates a new scenario object.
Attacks that exploit this kind of access
create_scenario. It is categorised as a Write tool in the Sablier MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sablier MCP Server MCP server in PolicyLayer and add a rule for create_scenario: 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.
create_scenario is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_scenario 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 create_scenario. 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.
create_scenario 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 →