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

uxi_delete_group

Delete a UXI group by ID; requires read-write access.

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/uxi-delete-group.md

What uxi_delete_group does on Hpe Networking

AI agents call uxi_delete_group 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 uxi_delete_group is rated Critical

This tool permanently removes a UXI group and its associated configuration, which cannot be recovered. While the blast radius depends on group scope (potentially affecting multiple users/devices if the group is large), the destructive nature of deletion places it in the Destructive category rather than Write. The requirement for 'read-write access' confirms elevated permissions needed for this operation.

From the tool's definition 'Delete a UXI group by ID' — the verb 'delete' indicates irreversible removal of data. The description explicitly states the action cannot be undone.

Questions about uxi_delete_group

What does the uxi_delete_group tool do? +

Delete a UXI group by ID; requires read-write access. 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 uxi_delete_group? +

Register the Hpe Networking MCP server in PolicyLayer and add a rule for uxi_delete_group: 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 uxi_delete_group? +

uxi_delete_group 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 uxi_delete_group? +

Yes. Add a rate_limit block to the uxi_delete_group 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 uxi_delete_group completely? +

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

uxi_delete_group 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.