release_environment
Stop and destroy an environment owned by the authenticated agent before its TTL. Repeating release on an already released environment has no additional effect.
This record as markdown: /tools/nitrostack/release-environment.md
What release_environment does on Nitrostack
AI agents call release_environment to permanently remove resources in Nitrostack, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why release_environment is rated Critical
Destroys infrastructure resources irreversibly with no undo capability.
From the tool's definition Stop and destroy an environment, irreversible termination.
Attacks that exploit this kind of access
The rule that runs release_environment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For release_environment, this is the rule to start with:
release_environment is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Nitrostack, apply this rule, and every release_environment call is checked against it from then on.
Questions about release_environment
Stop and destroy an environment owned by the authenticated agent before its TTL. Repeating release on an already released environment has no additional effect. It is categorised as a Destructive tool in the Nitrostack MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nitrostack MCP server in PolicyLayer and add a rule for release_environment: 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 Nitrostack. Nothing to install.
release_environment 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 release_environment 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 release_environment. 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.
release_environment is provided by the Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nitrostack, and thousands of servers like it.
Across the catalogue