Compare named what-if scenarios against a base case, returning per-scenario outcome delta plus a sensitivity ranking showing which input variables move the outcome most across scenarios. Use for budget sensitivity analysis, deal what-ifs, capacity planning under multiple demand assumptions. The d...
Part of the Oraclaw server.
Free to start. No card required.
AI agents use simulate_scenario to create or modify resources in Oraclaw. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call simulate_scenario repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Oraclaw.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"simulate_scenario": {
"limits": [
{
"counter": "simulate_scenario_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Oraclaw policy for all 17 tools.
These attack patterns abuse exactly the kind of access simulate_scenario gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Compare named what-if scenarios against a base case, returning per-scenario outcome delta plus a sensitivity ranking showing which input variables move the outcome most across scenarios. Use for budget sensitivity analysis, deal what-ifs, capacity planning under multiple demand assumptions. The default outcome metric is the sum of input variables — supply scenarios that vary individual drivers to isolate their impact. For random sampling from a distribution, use simulate_montecarlo. Free.. It is categorised as a Write tool in the Oraclaw MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Oraclaw MCP server in PolicyLayer and add a rule for simulate_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 Oraclaw. Nothing to install.
simulate_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 simulate_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 simulate_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.
simulate_scenario is provided by the Oraclaw MCP server (@oraclaw/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 Oraclaw tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.