Calculate multiple moving averages (20, 50, 100, 200 period SMA/EMA).
AI agents call get_moving_averages to retrieve information from TradingView MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and computes technical analysis metrics (20, 50, 100, 200 period SMA/EMA moving averages) from existing market data. It is a read-only operation that produces analytical output without side effects, data modification, code execution, or financial commitments.
From the tool's definition Tool name 'get_moving_averages' and description 'Calculate multiple moving averages' indicates retrieval and computation of technical indicators from market data with no modification of data, no execution of arbitrary code, and no financial transactions.
Documented attack patterns abuse exactly the kind of access get_moving_averages gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TradingView MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_moving_averages:
{
"version": "1",
"default": "deny",
"tools": {
"get_moving_averages": {}
}
}get_moving_averages 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.
Calculate multiple moving averages (20, 50, 100, 200 period SMA/EMA). It is categorised as a Read tool in the TradingView MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TradingView MCP Server MCP server in PolicyLayer and add a rule for get_moving_averages: 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 Server. Nothing to install.
get_moving_averages 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 get_moving_averages 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 get_moving_averages. 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.
get_moving_averages is provided by the TradingView MCP Server MCP server (lev-corrupted/tradingviewmcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TradingView MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
33 TradingView MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.