Get detailed metadata about the current symbol (name, exchange, type, description)
AI agents call symbol_info to retrieve information from TradingView MCP Jackson without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries metadata about a trading symbol. It performs no side effects, does not modify data, execute code, delete anything, or commit financial transactions. It is a straightforward information lookup operation, consistent with the Read category.
From the tool's definition Tool name 'symbol_info' and description 'Get detailed metadata about the current symbol (name, exchange, type, description)' indicate retrieval of read-only symbol information with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get detailed metadata about the current symbol (name, exchange, type, description). It is categorised as a Read tool in the TradingView MCP Jackson MCP Server, which means it retrieves data without modifying state.
Register the TradingView MCP Jackson MCP server in PolicyLayer and add a rule for symbol_info: 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 Jackson. Nothing to install.
symbol_info 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 symbol_info 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 symbol_info. 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.
symbol_info is provided by the TradingView MCP Jackson MCP server (nimit791/tradingview-mcp-jackson). 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 →