AI agents call vm_query to retrieve information from VictoriaMetrics-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 time series data from VictoriaMetrics without modifying, deleting, or executing operations. It is a straightforward read operation that returns metric values. The blast radius of misuse is minimal—an attacker could only exfiltrate or analyze metric data, not alter system state or cause data loss.
From the tool's definition Tool name 'vm_query' and description 'Query current value of a time series' indicate a retrieval operation with no side effects. The verb 'query' combined with 'current value' signals a read-only data retrieval action typical of monitoring/metrics systems.
Documented attack patterns abuse exactly the kind of access vm_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VictoriaMetrics-mcp-server, and nothing reaches the server without passing your rules. This is the rule we recommend for vm_query:
{
"version": "1",
"default": "deny",
"tools": {
"vm_query": {}
}
}vm_query 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.
Query current value of a time series. It is categorised as a Read tool in the VictoriaMetrics-mcp-server MCP Server, which means it retrieves data without modifying state.
Register the VictoriaMetrics-mcp-server MCP server in PolicyLayer and add a rule for vm_query: 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-mcp-server. Nothing to install.
vm_query 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 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. 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 is provided by the VictoriaMetrics-mcp-server 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.
Start from VictoriaMetrics-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.
6 VictoriaMetrics-mcp-server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.