New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_glp_role_assignment

Delete an RBAC role assignment by ID.

SERVERHpe Networking SOURCEsecure-ssid/hpe-networking-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hpe-networking-mcp/delete-glp-role-assignment.md

What delete_glp_role_assignment does on Hpe Networking

AI agents call delete_glp_role_assignment to permanently remove resources in Hpe Networking, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_glp_role_assignment is rated Critical

This tool performs an irreversible deletion of an RBAC (Role-Based Access Control) role assignment. Deleting role assignments cannot be undone without manual recreation and can immediately revoke user access to network resources, causing operational disruption. This qualifies as Destructive rather than Write because the action cannot be reversed programmatically.

From the tool's definition Tool name contains 'delete'; description states 'Delete an RBAC role assignment by ID.' The action irreversibly removes access control configuration.

Questions about delete_glp_role_assignment

What does the delete_glp_role_assignment tool do? +

Delete an RBAC role assignment by ID. It is categorised as a Destructive tool in the Hpe Networking MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_glp_role_assignment? +

Register the Hpe Networking MCP server in PolicyLayer and add a rule for delete_glp_role_assignment: 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 Hpe Networking. Nothing to install.

What risk level is delete_glp_role_assignment? +

delete_glp_role_assignment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_glp_role_assignment? +

Yes. Add a rate_limit block to the delete_glp_role_assignment 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.

How do I block delete_glp_role_assignment completely? +

Set action: deny in the PolicyLayer policy for delete_glp_role_assignment. 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.

What MCP server provides delete_glp_role_assignment? +

delete_glp_role_assignment is provided by the Hpe Networking MCP server (secure-ssid/hpe-networking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Hpe Networking, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hpe Networking's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.