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 d...
Part of the Invarium server.
Free to start. No card required.
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. PolicyLayer 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. PolicyLayer 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.
{
"version": "1",
"default": "deny",
"hide": [
"invarium_delete_agent"
]
}See the full Invarium policy for all 19 tools.
These attack patterns abuse exactly the kind of access invarium_delete_agent gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
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.
Register the Invarium MCP server in PolicyLayer and add a rule for invarium_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 Invarium. Nothing to install.
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 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 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). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 Invarium tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.