Low Risk

pve_list_lxc_containers

List LXC containers.

Part of the Nandi Proxmox server.

pve_list_lxc_containers is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE NANDI PROXMOX →

Free to start. No card required.

AI agents call pve_list_lxc_containers to retrieve information from Nandi Proxmox without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though pve_list_lxc_containers only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "pve_list_lxc_containers": {}
  }
}

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_list_lxc_containers 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_list_lxc_containers only ever does what you allow.

SECURE NANDI PROXMOX →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the pve_list_lxc_containers tool do? +

List LXC containers.. It is categorised as a Read tool in the Nandi Proxmox MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pve_list_lxc_containers? +

Register the Nandi Proxmox MCP server in PolicyLayer and add a rule for pve_list_lxc_containers: 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_list_lxc_containers? +

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

Can I rate-limit pve_list_lxc_containers? +

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

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

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