Execute a trade action in replay mode (buy, sell, or close position)
AI agents invoke replay_trade to trigger actions in TradingView MCP Bridge. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes trade actions whose real-world effects depend on arguments. While 'replay mode' suggests it may be simulated rather than live trading, the core capability is Execute—it triggers external operations with side effects. It does not merely read data (Read), nor is it a simple reversible modification (Write), nor does it permanently delete data (Destructive).
From the tool's definition The tool description states it "Execute[s] a trade action" which involves running a command that triggers external operations (buy, sell, or close position). The effects depend directly on the arguments passed (which action and position details).
Documented attack patterns abuse exactly the kind of access replay_trade 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 replay_trade:
{
"version": "1",
"default": "deny",
"tools": {
"replay_trade": {
"limits": [
{
"counter": "replay_trade_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}replay_trade stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute a trade action in replay mode (buy, sell, or close position). It is categorised as a Execute tool in the TradingView MCP Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TradingView MCP Bridge MCP server in PolicyLayer and add a rule for replay_trade: 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.
replay_trade is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the replay_trade 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 replay_trade. 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.
replay_trade 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.