run_strategy_backtest · Nubra MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_strategy_backtest does on Nubra MCP Server

AI agents invoke run_strategy_backtest to trigger actions in Nubra MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_strategy_backtest needs a policy

This tool runs code (backtesting engine) triggered by user-supplied strategy rules. While backtesting against historical data is read-only regarding market data, the execution of arbitrary strategy logic constitutes code execution. It is not Destructive (no data deletion), Financial (no real trades or money movement — explicitly 'UAT environment'), or Write (does not persistently modify user data).

From the tool's definition Tool description states 'Run a NubraOSS-style rule-based strategy backtest' — this executes a strategy against historical data, triggering computation and analysis whose effects depend on the strategy parameters provided as arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_strategy_backtest Rate-limited

run_strategy_backtest stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_strategy_backtest": {
      "limits": [
        {
          "counter": "run_strategy_backtest_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Nubra MCP Server, so you can run agents against it safely.

FAQ

Questions about run_strategy_backtest

What does the run_strategy_backtest tool do? +

Run a NubraOSS-style rule-based strategy backtest using the current Nubra login/session and Nubra historical data only. It is categorised as a Execute tool in the Nubra MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_strategy_backtest? +

Register the Nubra MCP Server MCP server in PolicyLayer and add a rule for run_strategy_backtest: 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 Nubra MCP Server. Nothing to install.

What risk level is run_strategy_backtest? +

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

Can I rate-limit run_strategy_backtest? +

Yes. Add a rate_limit block to the run_strategy_backtest 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.

How do I block run_strategy_backtest completely? +

Set action: deny in the PolicyLayer policy for run_strategy_backtest. 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 run_strategy_backtest? +

run_strategy_backtest is provided by the Nubra MCP Server MCP server (socials-zanskar/nubra-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.