Delete a role from the application
AI agents call delete_role to permanently remove resources in HAP MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a role is a destructive operation that cannot be undone and affects access control across the application. This is more severe than Write (which is reversible) but may not be Financial unless the role has direct financial implications. The blast radius is significant because removing a role could break workflows, disable user access, and require administrative intervention to restore.
From the tool's definition Tool name is 'delete_role' with description 'Delete a role from the application'. The verb 'delete' indicates irreversible removal of data (a role and its associated permissions/memberships).
Attacks that exploit this kind of access
Delete a role from the application. It is categorised as a Destructive tool in the HAP MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the HAP 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 HAP 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 HAP MCP Server MCP server (mingdaocloud/hap-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →