Historial de trades del sistema con estadísticas.
AI agents call trader_history 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 queries historical trading data and statistics without making changes to positions, executing orders, or performing destructive operations. It is a read-only operation that provides historical information for analysis purposes.
From the tool's definition Tool name 'trader_history' and description 'Historial de trades del sistema con estadísticas' (History of trades of the system with statistics) indicates retrieval of historical trading data and statistics.
Attacks that exploit this kind of access
Historial de trades del sistema con estadísticas. 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_history: 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_history 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_history 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_history. 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_history 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 →