This record as markdown: /tools/gethosthewalrus-proxmox-mcp/list-roles.md
What list_roles does on Proxmox MCP Server
AI agents call list_roles to retrieve information from Proxmox MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_roles is rated Low
This tool performs a read-only operation to enumerate available roles in the Proxmox VE system. It has no side effects, does not execute commands, does not modify data, and does not involve financial transactions. The blast radius of misuse is minimal—an AI agent could only enumerate roles that likely should be visible to authenticated users anyway.
From the tool's definition Tool name 'list_roles' and description 'List all available roles' indicate a query operation that retrieves role information without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
The rule that runs list_roles safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Proxmox MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_roles, this is the rule to start with:
list_roles is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every list_roles call is checked against it from then on.
Questions about list_roles
List all available roles. It is categorised as a Read tool in the Proxmox MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for list_roles: 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 Proxmox MCP Server. Nothing to install.
list_roles is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_roles 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.
Set action: deny in the PolicyLayer policy for list_roles. 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.
list_roles is provided by the Proxmox MCP Server MCP server (gethosthewalrus/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Proxmox MCP Server, and thousands of servers like it.
This server
Across the catalogue