backtest_strategy · Tradingview MCP: Risk & Policy

WHAT IT DOES

What backtest_strategy does on Tradingview

AI agents invoke backtest_strategy to trigger actions in Tradingview. 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 backtest_strategy needs a policy

Backtesting strategies typically involves executing simulated trades or running computational models against historical data, which falls under Execute. The server description explicitly mentions 'backtesting' as a core feature. However, since the description is empty, there is uncertainty about whether it merely reads/queries historical data or actively runs trading simulations.

From the tool's definition Tool name 'backtest_strategy' on a trading/backtesting server; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

backtest_strategy Rate-limited

backtest_strategy 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": {
    "backtest_strategy": {
      "limits": [
        {
          "counter": "backtest_strategy_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 Tradingview, so you can run agents against it safely.

FAQ

Questions about backtest_strategy

What does the backtest_strategy tool do? +

backtest_strategy. It is categorised as a Execute tool in the Tradingview MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on backtest_strategy? +

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

What risk level is backtest_strategy? +

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

Can I rate-limit backtest_strategy? +

Yes. Add a rate_limit block to the backtest_strategy 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 backtest_strategy completely? +

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

backtest_strategy is provided by the Tradingview MCP server (mrxjeus-cpu/trading-mcp-bot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.