batch_run

Run an action across multiple symbols and/or timeframes

SERVERTradingView MCP Server SOURCEdebarpan2000/tradingview-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/debarpan2000-tradingview-mcp/batch-run.md

WHAT IT DOES

What batch_run does on TradingView MCP Server

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

RISK

Why batch_run is rated High

batch_run is an Execute category tool because it triggers external operations (actions on TradingView charts) whose effects depend on user-supplied arguments (which symbols, timeframes, and which action). While individual actions might be Write or Read, the batch execution pattern and the fact that it orchestrates side effects across multiple targets elevates this to Execute.

From the tool's definition Tool performs 'Run an action across multiple symbols and/or timeframes' — executes actions with side effects determined by the action argument across potentially many targets.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs batch_run safely

PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For batch_run, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Server, apply this rule, and every batch_run call is checked against it from then on.

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 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 batch_run? +

Register the TradingView MCP Server 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 Server. 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 MCP server (debarpan2000/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on TradingView MCP Server, and thousands of servers like it.

This server

All 78 TradingView MCP Server tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP →qt_batch on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →