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

uxi_delete_agent

Delete/decommission a UXI agent by ID; requires read-write access.

SERVERAPI-Central SOURCEsecure-ssid/centralmcp
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/secure-ssid-centralmcp/uxi-delete-agent.md

What uxi_delete_agent does on API-Central

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

The tool permanently removes a UXI agent from the system, which cannot be undone without recovery procedures. This is an irreversible deletion operation, making it Destructive rather than Write. The impact is significant in a network operations context where agents are critical infrastructure components, warranting high severity.

From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete/decommission a UXI agent by ID' — irreversible removal of an agent resource.

Questions about uxi_delete_agent

What does the uxi_delete_agent tool do? +

Delete/decommission a UXI agent 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.

How do I enforce a policy on uxi_delete_agent? +

Register the API-Central MCP server in PolicyLayer and add a rule for uxi_delete_agent: 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.

What risk level is uxi_delete_agent? +

uxi_delete_agent 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_agent? +

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

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

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

// 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 API-Central'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.