Query time series over a time range
AI agents call vm_query_range to retrieve information from Victoriametrics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation on time series data within a specified time range. It retrieves metrics from the database but does not create, modify, delete, or execute code. The action is non-destructive and has no financial impact. The severity is low because metrics data is typically not sensitive in most contexts, and querying poses minimal risk of unintended consequences.
From the tool's definition Tool name 'vm_query_range' and description 'Query time series over a time range' indicate retrieval of time series data from VictoriaMetrics without modification or side effects.
Attacks that exploit this kind of access
Query time series over a time range. It is categorised as a Read tool in the Victoriametrics MCP Server, which means it retrieves data without modifying state.
Register the Victoriametrics MCP server in PolicyLayer and add a rule for vm_query_range: 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 Victoriametrics. Nothing to install.
vm_query_range 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 vm_query_range 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 vm_query_range. 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.
vm_query_range is provided by the Victoriametrics MCP server (@yincongcyincong/victoriametrics-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →