This record as markdown: /tools/rsp2k-mcp-vultr/get-cdn-zone-stats.md
What get_cdn_zone_stats does on Vultr MCP
AI agents call get_cdn_zone_stats to retrieve information from Vultr MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_cdn_zone_stats is rated Low
This tool retrieves CDN zone statistics without modifying infrastructure. The absence of a description lowers confidence slightly, but the naming convention ('get_') and context of CDN management tools strongly indicate read-only operation that queries existing metrics. No side effects or resource modifications are implied.
From the tool's definition Tool name 'get_cdn_zone_stats' indicates retrieval of statistics/metrics data. The 'get_' prefix is a standard read operation pattern.
Attacks that exploit this kind of access
The rule that runs get_cdn_zone_stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vultr MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_cdn_zone_stats, this is the rule to start with:
get_cdn_zone_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vultr MCP, apply this rule, and every get_cdn_zone_stats call is checked against it from then on.
Questions about get_cdn_zone_stats
get_cdn_zone_stats is a read tool on the Vultr MCP server. It is categorised as a Read tool in the Vultr MCP MCP Server, which means it retrieves data without modifying state.
Register the Vultr MCP server in PolicyLayer and add a rule for get_cdn_zone_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 Vultr MCP. Nothing to install.
get_cdn_zone_stats 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_cdn_zone_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.
Set action: deny in the PolicyLayer policy for get_cdn_zone_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.
get_cdn_zone_stats is provided by the Vultr MCP server (rsp2k/mcp-vultr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vultr, and thousands of servers like it.
This server
Across the catalogue