AI agents use vm_data_write to create or update resources in VictoriaMetrics-mcp-server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VictoriaMetrics-mcp-server environment.
This tool writes data to the VictoriaMetrics database. While this is a write operation (creating/modifying time-series data), it is potentially reversible and does not delete data. However, it carries high severity because an AI agent could write large volumes of incorrect or malicious data, corrupting the metrics database, causing alerting failures, or impacting monitoring systems that depend on accurate data.
From the tool's definition Tool name 'vm_data_write' and description 'Write data to the VM database' clearly indicate a write operation to a database.
Documented attack patterns abuse exactly the kind of access vm_data_write 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_data_write:
{
"version": "1",
"default": "deny",
"tools": {
"vm_data_write": {
"limits": [
{
"counter": "vm_data_write_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}vm_data_write stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Write data to the VM database. It is categorised as a Write tool in the VictoriaMetrics-mcp-server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the VictoriaMetrics-mcp-server MCP server in PolicyLayer and add a rule for vm_data_write: 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_data_write is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vm_data_write 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_data_write. 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_data_write 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.