batch_run · TradingView MCP: Risk & Policy

WHAT IT DOES

What batch_run does on TradingView MCP

AI agents invoke batch_run to trigger actions in TradingView MCP. 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 batch_run needs a policy

This tool executes user-specified actions across multiple financial instruments and timeframes, making it an Execute category tool. Severity is medium rather than high because the blast radius is limited to TradingView operations (no actual financial transactions executed by this tool itself, though it could trigger trading-related automations).

From the tool's definition Tool performs 'Run an action across multiple symbols and/or timeframes' — this executes operations with effects dependent on which actions and symbols are specified. The phrase 'run an action' indicates code/command execution.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_run Rate-limited

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

FAQ

Questions about batch_run

What does the batch_run tool do? +

Run an action across multiple symbols and/or timeframes. It is categorised as a Execute tool in the TradingView MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on batch_run? +

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

What risk level is batch_run? +

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

Can I rate-limit batch_run? +

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

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

batch_run is provided by the TradingView MCP server (ulianbass/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.