Run a custom BACKTEST strategy provided by the AI agent using historical data fetched from BlinkX SmartAPI. historical data will be available in variable historical_data in format historical_data.append({ "timestamp": candle[0], # The timestamp is the first element "open": candle...
Part of the Blinkxmcp MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke run_backtest to trigger processes or run actions in Blinkxmcp. 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.
run_backtest 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.
tools:
run_backtest:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Blinkxmcp policy for all 12 tools.
Agents calling execute-class tools like run_backtest have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
run_backtest is one of the high-risk operations in Blinkxmcp. 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.
Run a custom BACKTEST strategy provided by the AI agent using historical data fetched from BlinkX SmartAPI. historical data will be available in variable historical_data in format historical_data.append({ "timestamp": candle[0], # The timestamp is the first element "open": candle[1], # Open is the second element "high": candle[2], # High is the third element "low": candle[3], # Low is the fourth element "close": candle[4], # Close is the fifth element "volume": candle[5] # Volume is the sixth element }) and for recording trades call record_trade(side: str, price: float, qty: int) that stores trades in variable RESULTS = {"trades": [], "metrics": {}} this variable will already be defined and can be read as it is Inputs: --------- backtest_code : str The Python code written by the AI agent. The code will be wrapped inside an async function and executed. instrument_token : str The instrument token to fetch historical candle data. from_time : str The starting timestamp for fetching historical candles (e.g., "2025-10-29+10:02:03"). to_time : str The ending timestamp for fetching historical candles (e.g., "2025-10-29+15:00:00"). session_id : str The session ID for fetching the token needed to call the API. Returns: -------- dict : The result of the backtest, including trade records and metrics.. It is categorised as a Execute tool in the Blinkxmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for run_backtest. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Blinkxmcp MCP server.
run_backtest is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_backtest 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.
Set action: deny in the Intercept policy for run_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.
run_backtest is provided by the Blinkxmcp MCP server (ai/blinkxmcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept