get_server_stats

THE RISK

Low Risk

Why get_server_stats needs a policy

This tool retrieves server statistics and performance metrics without modifying, executing operations, deleting data, or moving money. It is a straightforward read operation that queries internal server state for informational purposes only.

From the tool's definition Tool name is 'get_server_stats' and description states 'Get server statistics including API usage and cache performance.' The verb 'Get' combined with retrieval of operational metrics (API usage, cache performance) indicates data retrieval with no side…

Documented attack patterns abuse exactly the kind of access get_server_stats gives an agent:

POLICY

How to control get_server_stats

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_server_stats:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_server_stats": {}
  }
}

get_server_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register TradingView MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More TradingView MCP Server tools

Execute test_pine_script test_pine_script Execute validate_pine_script validate_pine_script Execute convert_pine_version convert_pine_version Read analyze_pair Comprehensive technical analysis for any symbol. Read autocomplete_pine autocomplete_pine Read calculate_correlation Calculate correlation between two forex pairs. Read detect_pine_version detect_pine_version Read detect_unfilled_gaps Detect unfilled price gaps (unfinished business areas).

All 33 TradingView MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_server_stats

What does the get_server_stats tool do? +

Get server statistics including API usage and cache performance. It is categorised as a Read tool in the TradingView MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_server_stats? +

Register the TradingView MCP Server MCP server in PolicyLayer and add a rule for get_server_stats: 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.

What risk level is get_server_stats? +

get_server_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_server_stats? +

Yes. Add a rate_limit block to the get_server_stats 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.

How do I block get_server_stats completely? +

Set action: deny in the PolicyLayer policy for get_server_stats. 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.

What MCP server provides get_server_stats? +

get_server_stats 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.

Enforce policy on every TradingView MCP Server tool call.

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.

CHECK YOUR STACK →