backtest_pine · PineForge-Codegen MCP: Risk & Policy

WHAT IT DOES

What backtest_pine does on PineForge-Codegen

AI agents invoke backtest_pine to trigger actions in PineForge-Codegen. 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_pine needs a policy

This tool executes code (Pine Script strategy code) whose effects depend entirely on the strategy's logic and arguments. While backtesting is deterministic and non-destructive to external systems, it involves running arbitrary code in a sandbox environment.

From the tool's definition Tool description states 'Run a real, deterministic backtest of a PineScript v6 strategy' and the server context indicates it 'transpiles Pine to C++ and runs it on the deterministic, TradingView-validated PineForge engine via Docker.' The tool executes…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

backtest_pine Rate-limited

backtest_pine 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_pine": {
      "limits": [
        {
          "counter": "backtest_pine_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 PineForge-Codegen, so you can run agents against it safely.

FAQ

Questions about backtest_pine

What does the backtest_pine tool do? +

Run a real, deterministic backtest of a PineScript v6 strategy — prefer this over. It is categorised as a Execute tool in the PineForge-Codegen 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_pine? +

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

What risk level is backtest_pine? +

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

Can I rate-limit backtest_pine? +

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

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

backtest_pine is provided by the PineForge-Codegen MCP server (oci:ghcr.io/pineforge-4pass/pineforge-codegen-mcp:v0.9.2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.