delete_agent

Permanently delete an agent and all associated data (requires agents:delete permission)

Server MoluAbi MCP Server oregpt/moluabi-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_agent does on MoluAbi MCP Server

AI agents call delete_agent to permanently remove resources in MoluAbi MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_agent needs a policy

This tool irreversibly deletes an agent and all its associated data. Destructive category applies because the action cannot be reversed or recovered. Severity is high because an AI agent misusing this tool could destroy user agents and their data with no recovery path, though impact is scoped to a specific agent rather than system-wide (which would be critical).

From the tool's definition Tool name is 'delete_agent' and description states 'Permanently delete an agent and all associated data' — the use of 'Permanently' and 'delete' clearly indicates irreversible data removal that cannot be undone.

Questions about delete_agent

What does the delete_agent tool do? +

Permanently delete an agent and all associated data (requires agents:delete permission). It is categorised as a Destructive tool in the MoluAbi MCP Server 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_agent? +

Register the MoluAbi MCP Server MCP server in PolicyLayer and add a rule for 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 MoluAbi MCP Server. Nothing to install.

What risk level is delete_agent? +

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

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

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

delete_agent is provided by the MoluAbi MCP Server MCP server (oregpt/moluabi-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.