High Risk →

simulate_drawdown

Simulate a hypothetical sequence of losses against a starting bankroll. Shows when daily loss and drawdown limits would trigger, and reports the maximum drawdown percentage reached.

Part of the Nephyr Risk MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

nephyr-risk Execute

AI agents invoke simulate_drawdown to trigger processes or run actions in Nephyr Risk. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

simulate_drawdown can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

nephyr-risk.yaml
tools:
  simulate_drawdown:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Nephyr Risk policy for all 7 tools.

Tool Name simulate_drawdown
Category Execute
Risk Level High

Agents calling execute-class tools like simulate_drawdown have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

simulate_drawdown is one of the high-risk operations in Nephyr Risk. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the simulate_drawdown tool do? +

Simulate a hypothetical sequence of losses against a starting bankroll. Shows when daily loss and drawdown limits would trigger, and reports the maximum drawdown percentage reached.. It is categorised as a Execute tool in the Nephyr Risk MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on simulate_drawdown? +

Add a rule in your Intercept YAML policy under the tools section for simulate_drawdown. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Nephyr Risk MCP server.

What risk level is simulate_drawdown? +

simulate_drawdown is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit simulate_drawdown? +

Yes. Add a rate_limit block to the simulate_drawdown rule in your Intercept 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.

How do I block simulate_drawdown completely? +

Set action: deny in the Intercept policy for simulate_drawdown. 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.

What MCP server provides simulate_drawdown? +

simulate_drawdown is provided by the Nephyr Risk MCP server (nephyr-risk). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.