AI agents call layout_list 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 performs a simple query/retrieval of saved chart layouts with no side effects. It does not create, modify, delete data, nor execute external operations. The blast radius of misuse is minimal—an AI agent could only enumerate layouts it already has access to. Classification as Read is appropriate.
From the tool's definition Tool name 'layout_list' and description 'List saved chart layouts' indicate a read-only operation that retrieves existing layout data without modifying, deleting, or executing any operations.
Documented attack patterns abuse exactly the kind of access layout_list 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 layout_list:
{
"version": "1",
"default": "deny",
"tools": {
"layout_list": {}
}
}layout_list 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.
List saved chart layouts. 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 layout_list: 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.
layout_list 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 layout_list 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 layout_list. 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.
layout_list 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.