Place an order in the TradingView Trading Panel (paper trading OR live broker, depending on what
AI agents use trading_submit_order to commit financial operations through TradingView MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool places trading orders which can result in real financial transactions with a live broker. Even if paper trading is the default, the description explicitly acknowledges live broker execution is possible, making this a Financial category tool with critical severity since misuse could result in unintended real-money trades.
From the tool's definition Place an order in the TradingView Trading Panel (paper trading OR live broker, depending on what
Attacks that exploit this kind of access
Place an order in the TradingView Trading Panel (paper trading OR live broker, depending on what. It is categorised as a Financial tool in the TradingView MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the TradingView MCP server in PolicyLayer and add a rule for trading_submit_order: 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.
trading_submit_order is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the trading_submit_order 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 trading_submit_order. 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.
trading_submit_order 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →