Delete an environment.
AI agents call delete_environment_tool to permanently remove resources in Qiskit Gym 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 environment, which cannot be undone. In the context of a reinforcement learning quantum circuit synthesis system, deleting an environment destroys training data, configurations, and learned models associated with that environment. This is irreversible data loss, making it destructive.
From the tool's definition Tool name contains 'delete' and description states 'Delete an environment.' The verb 'delete' is explicitly destructive and irreversible.
Attacks that exploit this kind of access
Delete an environment. It is categorised as a Destructive tool in the Qiskit Gym MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Qiskit Gym 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 Gym MCP Server. Nothing to install.
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.
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.
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.
delete_environment_tool is provided by the Qiskit Gym MCP Server MCP server (qiskit-gym-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 →