High Risk →

pve_run_remote_diagnostic

Run safe diagnostic command in container.

Part of the Nandi Proxmox server.

pve_run_remote_diagnostic can trigger actions in Nandi Proxmox, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE NANDI PROXMOX →

Free to start. No card required.

AI agents invoke pve_run_remote_diagnostic to trigger processes or run actions in Nandi Proxmox. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

pve_run_remote_diagnostic can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "pve_run_remote_diagnostic": {
      "limits": [
        {
          "counter": "pve_run_remote_diagnostic_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Nandi Proxmox policy for all 25 tools.

Get this rule live on your own Nandi Proxmox server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY NANDI PROXMOX →

View all 25 tools →

These attack patterns abuse exactly the kind of access pve_run_remote_diagnostic gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so pve_run_remote_diagnostic only ever does what you allow.

SECURE NANDI PROXMOX →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the pve_run_remote_diagnostic tool do? +

Run safe diagnostic command in container.. It is categorised as a Execute tool in the Nandi Proxmox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pve_run_remote_diagnostic? +

Register the Nandi Proxmox MCP server in PolicyLayer and add a rule for pve_run_remote_diagnostic: 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 Nandi Proxmox. Nothing to install.

What risk level is pve_run_remote_diagnostic? +

pve_run_remote_diagnostic is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit pve_run_remote_diagnostic? +

Yes. Add a rate_limit block to the pve_run_remote_diagnostic 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 pve_run_remote_diagnostic completely? +

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

pve_run_remote_diagnostic is provided by the Nandi Proxmox MCP server (ezesc/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Nandi Proxmox tool call.

Deterministic rules across all 25 Nandi Proxmox tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.