Skip to main content
Glama

List ACL entries

proxmox_list_acl
Read-only

List Proxmox access control entries showing which role a user, group, or API token has on each path and whether it propagates to sub-paths; combine filters to narrow results.

Instructions

List access control entries: which role a user, group or API token has on which path (/, /vms/100, /storage/local, /pool/x, /nodes/pve1...) and whether it propagates to sub-paths. Filters combine. For what a user can effectively do, use proxmox_get_permissions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proxmox_list_acl"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoOnly entries on this path or below it, e.g. /vms or /vms/100
roleNoOnly entries granting this role
typeNoOnly entries of this subject type
userNoOnly entries for this user or API token ID (exact)
groupNoOnly entries for this group
limitNoMaximum number of results (default 1000)
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful semantics about what a returned row means and that propagation is reported, but with no output schema it does not describe the response shape or pagination/limit behavior, so the added value is moderate rather than rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the resource and its shape, followed by the disambiguation pointer. No filler or restated title text; every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an eight-parameter read-only list with no output schema, the definition covers the entry model, filter combination, and the main alternative tool. It stops short of describing result ordering or the default/maximum limit, though the schema supplies the limit values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 88%, so the schema already documents nearly every parameter and the baseline is 3. The description contributes the non-obvious AND semantics of combining filters, which is genuine added meaning, but it does not clarify the untyped 'fields' parameter or how path scoping interacts with sub-path propagation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb (list) and resource (access control entries) and then explains exactly what an entry contains: a role bound to a user, group or API token on a path, plus propagation. Concrete path examples (/, /vms/100, /storage/local, /pool/x, /nodes/pve1) make the resource scope unambiguous and separate it from permission-resolution tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes the agent: use proxmox_get_permissions when the question is what a user can effectively do, implying this tool is for raw stored ACL rows. It also states that filters combine, which tells the agent how to narrow results rather than guessing between alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools