vercel_delete_env
Delete a Vercel environment variable by its env id (get ids from vercel_get_env).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/vercel-delete-env.md
What vercel_delete_env does on UnClick
AI agents call vercel_delete_env to permanently remove resources in UnClick, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
envId | string | — | Alias for env_id. |
env_id | string | — | |
teamId | string | — | Alias for team_id. |
api_key | string | — | |
team_id | string | — | |
projectId | string | — | Alias for project_id. |
project_id | string | — |
Parameters from the server's own tool schema.
Why vercel_delete_env is rated Critical
This tool irreversibly removes configuration data from a production deployment system. Deleting environment variables can break applications, disable critical features, or compromise security if variables contain credentials. The action cannot be undone without manual restoration. While not directly financial, the potential for service disruption and business impact elevates this to high severity.
From the tool's definition Tool name includes 'delete' and description states 'Delete a Vercel environment variable by its env id'. Environment variables often contain secrets, API keys, database credentials, and other sensitive configuration required for application operation.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs vercel_delete_env safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vercel_delete_env, this is the rule to start with:
vercel_delete_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 UnClick, apply this rule, and every vercel_delete_env call is checked against it from then on.
Questions about vercel_delete_env
Delete a Vercel environment variable by its env id (get ids from vercel_get_env). It is categorised as a Destructive tool in the UnClick MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
vercel_delete_env accepts 7 parameters: envId, env_id, teamId, api_key, team_id, projectId, project_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for vercel_delete_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 UnClick. Nothing to install.
vercel_delete_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 vercel_delete_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 vercel_delete_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.
vercel_delete_env is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
Across the catalogue