Delete an agent with crypto payment
AI agents call atxp_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.
This tool permanently removes an agent from the system, which is irreversible and represents data destruction. While it involves a financial transaction (crypto payment), the primary destructive action (agent deletion) is the most severe consequence. The tool would prevent AI agents from accessing or recovering the deleted agent, and any agents dependent on it would break.
From the tool's definition Tool name explicitly uses 'delete' combined with description 'Delete an agent' - irreversible removal of an AI agent resource. The mention of 'crypto payment' indicates this deletion has financial implications.
Attacks that exploit this kind of access
Delete an agent with crypto payment. 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.
Register the MoluAbi MCP Server MCP server in PolicyLayer and add a rule for atxp_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.
atxp_delete_agent 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 atxp_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.
Set action: deny in the PolicyLayer policy for atxp_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.
atxp_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.
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 →