READ-ONLY. Get pending/working orders from the Trading Panel (if visible). Does NOT execute, modify, or cancel orders — only observes.
AI agents call trading_get_orders to retrieve information from TradingView MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves order data without side effects. The description explicitly restricts it to observation only, ruling out Execute, Write, Destructive, or Financial categories. While orders relate to financial instruments, the tool itself performs no financial action—it merely queries state. Classification as Read is appropriate.
From the tool's definition Tool name 'trading_get_orders' and description explicitly states 'READ-ONLY. Get pending/working orders from the Trading Panel (if visible). Does NOT execute, modify, or cancel orders — only observes.'
Attacks that exploit this kind of access
READ-ONLY. Get pending/working orders from the Trading Panel (if visible). Does NOT execute, modify, or cancel orders — only observes. It is categorised as a Read tool in the TradingView MCP MCP Server, which means it retrieves data without modifying state.
Register the TradingView MCP server in PolicyLayer and add a rule for trading_get_orders: 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_get_orders is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the trading_get_orders 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_get_orders. 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_get_orders 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 →