stock_options_chain
AI agents call stock_options_chain to retrieve information from Tradingview without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Options chain data is typically read-only market information that traders query for analysis. There is no indication this tool creates, modifies, deletes, executes code, or moves money. The name and server context (a toolkit for 'backtesting' and 'analysis') indicate data retrieval rather than order placement or account modifications. Lower confidence reflects the absence of explicit documentation.
From the tool's definition Tool name 'stock_options_chain' suggests retrieval of options chain data (a static market data structure). The trading toolkit context includes 'live sentiment, Yahoo Finance, and 30+ technical analysis tools' which are primarily Read operations.
Attacks that exploit this kind of access
stock_options_chain. It is categorised as a Read tool in the Tradingview MCP Server, which means it retrieves data without modifying state.
Register the Tradingview MCP server in PolicyLayer and add a rule for stock_options_chain: 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.
stock_options_chain 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 stock_options_chain 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 stock_options_chain. 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.
stock_options_chain is provided by the Tradingview MCP server (mrxjeus-cpu/trading-mcp-bot). 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 →