Run an action across multiple symbols and/or timeframes
AI agents invoke batch_run to trigger actions in TradingView MCP Bridge. 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.
This is an Execute-class tool because it runs actions whose effects depend on the specific arguments provided (which symbols, timeframes, and what action). While the sibling tools chart_set_symbol and chart_set_timeframe are themselves Execute tools (they trigger Chrome DevTools operations), batch_run compounds the risk by applying unknown actions across multiple contexts.
From the tool's definition The tool description states 'Run an action across multiple symbols and/or timeframes' which indicates execution of unspecified actions.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batch_run gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TradingView MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for batch_run:
{
"version": "1",
"default": "deny",
"tools": {
"batch_run": {
"limits": [
{
"counter": "batch_run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Run an action across multiple symbols and/or timeframes. It is categorised as a Execute tool in the TradingView MCP Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TradingView MCP Bridge 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 Bridge. Nothing to install.
batch_run 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 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.
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.
batch_run is provided by the TradingView MCP Bridge MCP server (tradesdontlie/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 78 TradingView MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
78 TradingView MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.