unset_env
Delete a DenkOps project's environment variable. Run redeploy to apply.
This record as markdown: /tools/denkopsai-mcp/unset-env.md
What unset_env does on Denkopsai
AI agents call unset_env to permanently remove resources in Denkopsai, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | Yes | |
project_id | string | Yes |
Parameters from the server's own tool schema.
Why unset_env is rated Critical
The tool permanently deletes an environment variable from a project. This is irreversible (the value is lost unless manually re-entered), and deleting environment variables can break running services, expose security gaps, or cause application failures. The instruction to 'Run redeploy to apply' confirms the change has real operational impact.
From the tool's definition "Delete a DenkOps project's environment variable"
Attacks that exploit this kind of access
The rule that runs unset_env safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Denkopsai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unset_env, this is the rule to start with:
unset_env 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 Denkopsai, apply this rule, and every unset_env call is checked against it from then on.
Questions about unset_env
Delete a DenkOps project's environment variable. Run redeploy to apply. It is categorised as a Destructive tool in the Denkopsai MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
unset_env accepts 2 parameters: key, project_id. Required: key, project_id. The full parameter table on this page comes from the server's own tool schema.
Register the Denkopsai MCP server in PolicyLayer and add a rule for unset_env: 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 Denkopsai. Nothing to install.
unset_env 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 unset_env 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 unset_env. 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.
unset_env is provided by the Denkopsai MCP server (@denkopsai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Denkopsai, and thousands of servers like it.
Across the catalogue