Manage a scenario: update its fields, delete it, or toggle its active state. IMPORTANT: Deletion is permanent and irreversible. When action="delete", you MUST first call this tool WITHOUT confirm=true. The tool will return a confirmation prompt listing the scenario to be deleted. Show this to the...
Part of the Invarium server.
Free to start. No card required.
AI agents may call invarium_manage_scenario 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_manage_scenario 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_manage_scenario"
]
}See the full Invarium policy for all 19 tools.
These attack patterns abuse exactly the kind of access invarium_manage_scenario 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.
Manage a scenario: update its fields, delete it, or toggle its active state. IMPORTANT: Deletion is permanent and irreversible. When action="delete", you MUST first call this tool WITHOUT confirm=true. The tool will return a confirmation prompt listing the scenario to be deleted. Show this to the user and only re-call with confirm=true after they explicitly approve. NEVER set confirm=true on the first call. NEVER delete multiple scenarios in a loop without showing the user the full list and getting one explicit confirmation for the batch. Args: scenario_id: ID of the scenario to manage. action: Operation to perform — "update", "delete", or "toggle". name: New name for the scenario (update only). description: New description for the scenario (update only). expected_behavior: New expected behavior text (update only). tags: JSON array string of tags, e.g. '["auth", "edge-case"]' (update only). confirm: Required for delete — must be true to execute deletion. First call without confirm to get a confirmation prompt. Returns: A confirmation string on success, or an error message on failure.. 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_manage_scenario: 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_manage_scenario 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_manage_scenario 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_manage_scenario. 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_manage_scenario 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.