deleteEnvironment tool can delete an environment for a given test target. The environment id is unique to the test target. The call is not reversible. an environment represents a specific setup or deployments for a test target. It include a test account when necsesary to login, a header configura...
AI agents call deleteEnvironment to permanently remove resources in Octomind — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (an environment and its configuration). The explicit statement that the operation is 'not reversible' confirms it cannot be undone. While the blast radius is significant (loss of test infrastructure configuration), it is scoped to a single environment rather than financial data or system-wide destruction, making it 'high' rather than 'critical' severity.
From the tool's definition Tool name is 'deleteEnvironment' and description explicitly states 'The call is not reversible.' It permanently removes an environment configuration including test accounts, headers, discovery URLs, and variables.
Documented attack patterns abuse exactly the kind of access deleteEnvironment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Octomind, and nothing reaches the server without passing your rules. This is the rule we recommend for deleteEnvironment:
{
"version": "1",
"default": "deny",
"hide": [
"deleteEnvironment"
]
}deleteEnvironment disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
deleteEnvironment tool can delete an environment for a given test target. The environment id is unique to the test target. The call is not reversible. an environment represents a specific setup or deployments for a test target. It include a test account when necsesary to login, a header configuration, a discovery url and a set of variables. It is categorised as a Destructive tool in the Octomind MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Octomind MCP server in PolicyLayer and add a rule for deleteEnvironment: 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 Octomind. Nothing to install.
deleteEnvironment 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 deleteEnvironment 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 deleteEnvironment. 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.
deleteEnvironment is provided by the Octomind MCP server (octomind-dev/octomind-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Octomind, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Octomind tools catalogued and risk-classified — across an index of 43,000+ MCP servers.