Skip to main content
Glama

pve_acl_prune

Remove or narrow over-broad ACL grants on Proxmox resources. Dry-run shows plan, then confirm to execute safely without widening access.

Instructions

MUTATION: prune (remove/narrow) an over-broad ACL grant flagged by pve_overbroad_grants.

Dry-run by default (returns a PLAN naming every principal losing/gaining what, and flagging shadow/widen gotchas); confirm=True executes and returns a dict. Non-atomic — a revoke PUT then an optional narrower re-grant PUT — but safe-direction: a partial failure only narrows access, never widens it. Synchronous. roleid = the over-broad role to remove (from detection).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoPrincipal type of target: 'user', 'group', or 'token'.user
pathYesResource path of the over-broad ACL entry to prune, e.g. '/'.
roleidNoThe over-broad role id to remove, as identified by pve_overbroad_grants.
targetYesPrincipal the over-broad grant belongs to: userid, groupid, or tokenid depending on kind.
confirmNoFalse (default) returns a dry-run PLAN preview; True executes the mutation.
narrow_pathNoOptional narrower path to scope the re-grant to, instead of the original path.
narrow_roleNoOptional narrower role id to re-grant in place of the removed one.
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 the description fully covers behavioral traits: mutation, dry-run default, return types (PLAN vs dict), non-atomic but safe-direction, synchronous execution. This exceeds the minimum requirement.

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

Conciseness4/5

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

The description is concise but could be more structured with bullet points. It front-loads the purpose and efficiently covers all key points 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 presence of an output schema, the description does not need to detail return values. It comprehensively covers purpose, usage, behavior, and parameters, leaving no major gaps for an AI agent to select and invoke the tool.

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

Parameters4/5

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

With 100% schema coverage, the description adds value by explaining roleid as 'the over-broad role to remove (from detection)' and clarifying the confirm flag's effect. This goes beyond the schema's basic descriptions.

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 prunes over-broad ACL grants flagged by pve_overbroad_grants. It uses specific verbs ('prune (remove/narrow)') and identifies the resource, distinguishing it from sibling tools like pve_acl_modify and pve_overbroad_grants.

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

Usage Guidelines4/5

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

The description explains dry-run default, execution with confirm=True, and the non-atomic safe-direction behavior. It references pve_overbroad_grants but does not explicitly contrast with when to use pve_acl_modify instead, leaving slight ambiguity.

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