trader_execute · Tradingview MCP: Risk & Policy

WHAT IT DOES

What trader_execute does on Tradingview

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

The tool triggers execution of a trading signal in TradingView, which constitutes an external operation with real market consequences. While it operates within TradingView's interface (via Chrome DevTools Protocol) rather than directly routing orders to a broker, executing trading signals can have financial implications.

From the tool's definition 'ejecuta la última señal STC pendiente en TradingView' — approves and executes a pending trading signal in TradingView

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

trader_execute Rate-limited

trader_execute 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_execute": {
      "limits": [
        {
          "counter": "trader_execute_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_execute

What does the trader_execute tool do? +

Aprueba y ejecuta la última señal STC pendiente en TradingView. Usar en modo MANUAL. 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_execute? +

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

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

Can I rate-limit trader_execute? +

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

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

trader_execute 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.

// THE FULL RECORD

trader_execute is one line of Tradingview's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →