vm_agent_set_password
Set a user password inside a VM via the guest agent.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/vm-agent-set-password.md
What vm_agent_set_password does on Proxmox MCP Server
AI agents invoke vm_agent_set_password to trigger actions in Proxmox MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why vm_agent_set_password is rated High
This tool executes an operation inside a running VM through the guest agent to modify a user's password. While it writes data (changes a password), the action is executed remotely inside a VM via an agent, making it Execute. It has high severity because compromising credentials inside a VM could allow privilege escalation, unauthorized access, or account takeover within the guest OS.
From the tool's definition Set a user password inside a VM via the guest agent
Attacks that exploit this kind of access
The rule that runs vm_agent_set_password safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Proxmox MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vm_agent_set_password, this is the rule to start with:
vm_agent_set_password stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every vm_agent_set_password call is checked against it from then on.
Questions about vm_agent_set_password
Set a user password inside a VM via the guest agent. It is categorised as a Execute tool in the Proxmox MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for vm_agent_set_password: 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 Proxmox MCP Server. Nothing to install.
vm_agent_set_password is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the vm_agent_set_password 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_agent_set_password. 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_agent_set_password is provided by the Proxmox MCP Server MCP server (gethosthewalrus/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Proxmox MCP Server, and thousands of servers like it.
Across the catalogue