Get indicator/study info and input values
AI agents call data_get_indicator 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 data about indicators and their input values without creating, modifying, deleting, or executing any trading operations. It is a passive data retrieval operation with no side effects, fitting the Read category. The severity is low because accessing indicator information poses minimal security risk even if misused by an AI agent.
From the tool's definition Tool name and description indicate retrieval of indicator and study information ('Get indicator/study info and input values'). The verb 'Get' and the read-only nature of querying existing indicator data without modification or execution.
Attacks that exploit this kind of access
Get indicator/study info and input values. 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 data_get_indicator: 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.
data_get_indicator 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 data_get_indicator 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 data_get_indicator. 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.
data_get_indicator 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 →