Delete an agent and all its associated data from Invarium. Permanently removes the agent, all generated test cases, test runs, and audit history. Requires confirm=True to prevent accidental deletion. IMPORTANT: This is a PERMANENT, DESTRUCTIVE action. Before calling, ALWAYS restate what will be...
Part of the Invarium MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents may call invarium_delete_agent to permanently remove or destroy resources in Invarium. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call invarium_delete_agent in a loop, permanently destroying resources in Invarium. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
tools:
invarium_delete_agent:
rules:
- action: deny
reason: "Blocked by default — enable with approval"See the full Invarium policy for all 19 tools.
Agents calling destructive-class tools like invarium_delete_agent have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.
invarium_delete_agent is one of the critical-risk operations in Invarium. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.
Delete an agent and all its associated data from Invarium. Permanently removes the agent, all generated test cases, test runs, and audit history. Requires confirm=True to prevent accidental deletion. IMPORTANT: This is a PERMANENT, DESTRUCTIVE action. Before calling, ALWAYS restate what will be deleted (agent name, test runs, scenarios, audit history) and require the user to explicitly say "yes" or "confirm". Never call with confirm=True on the first attempt. Args: agent_name: Name of the agent to delete. confirm: Must be True to proceed. Omit or set to False to get a confirmation prompt instead.. It is categorised as a Destructive tool in the Invarium MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Add a rule in your Intercept YAML policy under the tools section for invarium_delete_agent. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Invarium MCP server.
invarium_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 invarium_delete_agent rule in your Intercept 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 Intercept policy for invarium_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.
invarium_delete_agent is provided by the Invarium MCP server (invarium-ai/invarium). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept