uxi_delete_group
Delete a UXI group by ID; requires read-write access.
This record as markdown: /tools/secure-ssid-centralmcp/uxi-delete-group.md
What uxi_delete_group does on API-Central
AI agents call uxi_delete_group to permanently remove resources in API-Central, 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.
Attacks that exploit this kind of access
The rule that runs uxi_delete_group safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For uxi_delete_group, this is the rule to start with:
uxi_delete_group 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 API-Central, apply this rule, and every uxi_delete_group call is checked against it from then on.
Questions about uxi_delete_group
Delete a UXI group by ID; requires read-write access. It is categorised as a Destructive tool in the API-Central MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the API-Central 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 API-Central. Nothing to install.
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.
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.
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.
uxi_delete_group is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API-Central, and thousands of servers like it.
Across the catalogue