Estado completo del sistema STC: señal activa, posición abierta, heatmap de liquidaciones y P&L del día.
AI agents call trader_status 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 queries and returns data about trading positions, signals, and financial metrics without modifying anything. However, it exposes sensitive financial position and P&L information that could be misused if an agent acts on this data to make unauthorized trades or decisions.
From the tool's definition Tool retrieves system status information: 'Estado completo del sistema STC: señal activa, posición abierta, heatmap de liquidaciones y P&L del día' (complete system status, active signal, open position, liquidation heatmap, and day P&L).
Attacks that exploit this kind of access
Estado completo del sistema STC: señal activa, posición abierta, heatmap de liquidaciones y P&L del día. 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_status: 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_status 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_status 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_status. 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_status 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 →