This record as markdown: /tools/gethosthewalrus-proxmox-mcp/delete-role.md
What delete_role does on Proxmox MCP Server
AI agents call delete_role to permanently remove resources in Proxmox MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_role is rated Critical
Deletion of roles is a destructive operation that cannot be undone. Removing a role could revoke permissions for users or groups, disrupt access control, and potentially lock users out of infrastructure management. While not as immediately catastrophic as deleting VMs or storage, role deletion is irreversible and impacts system security posture.
From the tool's definition Tool name is 'delete_role' with description 'Delete a role.' The verb 'delete' indicates irreversible removal of data (a role object in Proxmox).
Attacks that exploit this kind of access
The rule that runs delete_role 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 delete_role, this is the rule to start with:
delete_role is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every delete_role call is checked against it from then on.
Questions about delete_role
Delete a role. It is categorised as a Destructive tool in the Proxmox MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for delete_role: 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.
delete_role is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_role 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 delete_role. 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.
delete_role 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.
Across the catalogue