trader_pause · Tradingview MCP: Risk & Policy

WHAT IT DOES

What trader_pause does on Tradingview

AI agents invoke trader_pause 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 trader_pause needs a policy

This tool halts the execution of trading signals in what appears to be an automated trading workflow connected to TradingView. While it doesn't directly move money, pausing signal execution in a live trading environment has significant financial implications — missed trades, open positions unmanaged, or disrupted strategies. It triggers an external operational state change.

From the tool's definition Pausa el sistema: no ejecuta nuevas señales hasta reanudar — 'pausa el sistema' and 'no ejecuta nuevas señales' indicate this controls execution flow of a trading signal system

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

trader_pause Rate-limited

trader_pause 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": {
    "trader_pause": {
      "limits": [
        {
          "counter": "trader_pause_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 trader_pause

What does the trader_pause tool do? +

Pausa el sistema: no ejecuta nuevas señales hasta reanudar. 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 trader_pause? +

Register the Tradingview MCP server in PolicyLayer and add a rule for trader_pause: 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 trader_pause? +

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

Can I rate-limit trader_pause? +

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

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

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