vm_agent_exec_status

Get the status/result of a command previously executed via the guest agent.

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gethosthewalrus-proxmox-mcp/vm-agent-exec-status.md

WHAT IT DOES

What vm_agent_exec_status does on Proxmox MCP Server

AI agents call vm_agent_exec_status to retrieve information from Proxmox MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why vm_agent_exec_status is rated Low

This tool retrieves the result/status of a previously executed command. It queries state information about command execution without creating, modifying, deleting, or triggering new operations. The tool only reads and returns data about past execution, making it a Read category risk with low severity since it cannot cause infrastructure changes or side effects.

From the tool's definition Tool name contains 'status' and description states 'Get the status/result of a command previously executed'. The verb 'Get' and 'status' indicate retrieval of information without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vm_agent_exec_status 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_exec_status, this is the rule to start with:

vm_agent_exec_status Allowed

vm_agent_exec_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vm_agent_exec_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every vm_agent_exec_status call is checked against it from then on.

FAQ

Questions about vm_agent_exec_status

What does the vm_agent_exec_status tool do? +

Get the status/result of a command previously executed via the guest agent. It is categorised as a Read tool in the Proxmox MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vm_agent_exec_status? +

Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for vm_agent_exec_status: 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.

What risk level is vm_agent_exec_status? +

vm_agent_exec_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit vm_agent_exec_status? +

Yes. Add a rate_limit block to the vm_agent_exec_status 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.

How do I block vm_agent_exec_status completely? +

Set action: deny in the PolicyLayer policy for vm_agent_exec_status. 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.

What MCP server provides vm_agent_exec_status? +

vm_agent_exec_status 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.

KEEP EXPLORING

More on Proxmox MCP Server, and thousands of servers like it.

This server

All 286 Proxmox MCP Server tools →

Across the catalogue

claude_git_status on Claude Bridge →get_agent on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →