Critical Risk →

delete_environment_tool

Delete an environment.

How to control delete_environment_tool ↓

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

Critical Risk

An AI agent that decides to call delete_environment_tool doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Qiskit MCP Server is gone — there is no undo for destructive operations.

Documented attack patterns abuse exactly the kind of access delete_environment_tool gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Qiskit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_environment_tool:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_environment_tool"
  ]
}

delete_environment_tool disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Qiskit MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete_environment_tool tool do? +

Delete an environment. It is categorised as a Destructive tool in the Qiskit 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_environment_tool? +

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

What risk level is delete_environment_tool? +

delete_environment_tool 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_environment_tool? +

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

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

delete_environment_tool is provided by the Qiskit MCP Server MCP server (qiskit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Qiskit MCP Server tool call.

Deterministic rules across all 71 Qiskit MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

71 Qiskit MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.