Get indicator/study info and input values
AI agents call data_get_indicator to retrieve information from TradingView MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing indicator data and configuration without modifying any state. It is a query-like operation that has no side effects on charts, trades, or the system. Read operations pose minimal risk unless they expose sensitive information, but indicator data is typically non-sensitive analytical metadata. Severity is low given the read-only nature and low blast radius of misuse.
From the tool's definition Tool name and description indicate retrieval of indicator/study information and input values. Uses verb 'Get' which is explicitly listed as a Read operation (get, fetch). No modification, deletion, or execution of trades/code is implied.
Documented attack patterns abuse exactly the kind of access data_get_indicator gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TradingView MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for data_get_indicator:
{
"version": "1",
"default": "deny",
"tools": {
"data_get_indicator": {}
}
}data_get_indicator is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get indicator/study info and input values. It is categorised as a Read tool in the TradingView MCP Bridge MCP Server, which means it retrieves data without modifying state.
Register the TradingView MCP Bridge 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 Bridge. 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 Bridge MCP server (tradesdontlie/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 78 TradingView MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
78 TradingView MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.