Skip to main content
Glama

pve_acl_modify

Grant or revoke Proxmox ACL entries with dry-run preview to avoid shadow or widen effects. Execute with confirmation to apply changes.

Instructions

MUTATION: grant or revoke an ACL entry (PUT /access/acl).

Dry-run by default (returns a PLAN) — it surfaces the critical Proxmox gotcha: a specific-path ACL REPLACES inherited grants (SHADOW) and revoking can RESTORE them (WIDEN). confirm=True executes and returns a dict; synchronous, no UPID. Use pve_acl_list to see current entries, pve_overbroad_grants to find over-broad ones, or pve_acl_prune to narrow/remove one.

kind='user' (default), 'group', or 'token'. delete=False = grant; delete=True = revoke.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoPrincipal type of target: 'user', 'group', or 'token'.user
pathYesResource path the ACL entry applies to, e.g. '/vms/100' or '/'.
rolesYesComma-separated role id(s) to grant or revoke, e.g. 'PVEVMAdmin'.
deleteNoFalse to grant the roles, True to revoke them.
targetYesPrincipal the ACL entry applies to: userid, groupid, or tokenid depending on kind.
confirmNoFalse (default) returns a dry-run PLAN preview; True executes the mutation.
propagateNoWhether the grant propagates to child paths below `path`.
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. Discloses mutation, dry-run default, synchronous execution, no UPID, and the critical Proxmox gotcha about ACL shadowing and widening.

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?

Concise and well-structured, front-loading the purpose and key behavior. Every sentence adds essential information without unnecessary verbosity.

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

Completeness5/5

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

Given the complexity (8 parameters, 3 required) and presence of output schema, the description comprehensively covers mutation behavior, default dry-run, parameter details, and the Proxmox gotcha. No gaps.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds value by explaining the default kind, the mapping of delete to grant/revoke, confirm behavior, and the purpose of proximo_target.

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 clearly states the tool is a mutation to grant or revoke an ACL entry, specifying the REST endpoint and distinguishing from sibling tools like pve_acl_list, pve_overbroad_grants, and pve_acl_prune.

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?

Explicitly mentions dry-run by default and confirm=True for execution. Provides guidance on when to use alternatives: pve_acl_list to see entries, pve_overbroad_grants to find over-broad ones, and pve_acl_prune to narrow/remove.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server