// SCAN REPORT

VictoriaMetrics-mcp-server

6 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 12 Jun 2026

2 can modify or destroy data

4 read-only

6 tools total

Community server · catalogue entry verified 12/06/2026

How to control VictoriaMetrics-mcp-server ↓

TOOL MAP

What VictoriaMetrics-mcp-server exposes to your agents

Read (4) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous VictoriaMetrics-mcp-server tools

Write · Medium vm_prometheus_write This tool writes/imports time-series data into VictoriaMetrics. Write · High vm_data_write This tool writes data to the VictoriaMetrics database.

2 of VictoriaMetrics-mcp-server's 6 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control VictoriaMetrics-mcp-server

PolicyLayer is an MCP gateway — it sits between your AI agents and VictoriaMetrics-mcp-server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "vm_data_write": {
    "limits": [
      {
        "counter": "vm_data_write_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "vm_label_values": {
    "limits": [
      {
        "counter": "vm_label_values_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register VictoriaMetrics-mcp-server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON VICTORIAMETRICS-MCP-SERVER →

Free to start. No card required.

FULL CATALOGUE

All 6 VictoriaMetrics-mcp-server tools

WRITE 2 tools

Write vm_data_write Write data to the VM database Write vm_prometheus_write mport Prometheus exposition format data into VictoriaMetrics

READ 4 tools

Read vm_label_values Get all unique values for a specific label Read vm_labels Get all unique label names Read vm_query Query current value of a time series Read vm_query_range Query time series over a time range

FAQ

Questions about VictoriaMetrics-mcp-server

How do I prevent bulk modifications through VictoriaMetrics-mcp-server? +

The VictoriaMetrics-mcp-server server has 2 write tools including vm_data_write, vm_prometheus_write. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach VictoriaMetrics-mcp-server.

How many tools does the VictoriaMetrics-mcp-server MCP server expose? +

6 tools across 2 categories: Read, Write. 4 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on VictoriaMetrics-mcp-server? +

Register the VictoriaMetrics-mcp-server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every VictoriaMetrics-mcp-server tool call.

Deterministic rules across all 6 VictoriaMetrics-mcp-server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON VICTORIAMETRICS-MCP-SERVER →

Free to start. No card required.

6 VictoriaMetrics-mcp-server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.