Detalles de la última señal STC y su análisis de liquidación.
AI agents call trader_last_signal 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.
This tool retrieves and reports on past trading signals and their analysis. It queries state without triggering trades, modifying data, or executing commands. The worst case misuse is viewing signal details that may inform a poor trading decision, but the tool itself performs no irreversible actions, no code execution, and no financial transactions.
From the tool's definition Tool name 'trader_last_signal' and description 'Detalles de la última señal STC y su análisis de liquidación' (Details of the last STC signal and its liquidation analysis) indicates retrieval of historical signal data.
Attacks that exploit this kind of access
Detalles de la última señal STC y su análisis de liquidación. 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 trader_last_signal: 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.
trader_last_signal 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 trader_last_signal 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 trader_last_signal. 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.
trader_last_signal is provided by the Tradingview MCP server (lionfaion/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 →