stock_extended_hours
AI agents call stock_extended_hours 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.
Given the server's purpose (trading toolkit with analysis and backtesting), this tool most likely retrieves or queries market data about stocks trading outside regular hours. No evidence suggests it modifies data, executes commands, or causes financial transactions.
From the tool's definition Tool name 'stock_extended_hours' suggests querying extended hours trading data for stocks. The empty description limits certainty, but the name pattern (noun-focused, parallel to sibling tools like 'bitcoin_market_pulse' and 'coin_analysis') indicates data…
Attacks that exploit this kind of access
stock_extended_hours. 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_extended_hours: 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_extended_hours 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_extended_hours 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_extended_hours. 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_extended_hours 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 →