Delete a Vercel environment variable by its env id (get ids from vercel_get_env).
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 |
|---|---|---|---|
env_id | string | Yes | |
api_key | string | — | |
team_id | string | — | |
project_id | string | Yes |
Parameters from the server's own tool schema.
This tool permanently removes environment variables from Vercel deployments. Environment variables often contain secrets, API keys, database credentials, and other critical configuration. Deletion is irreversible and could break application functionality, expose systems to misconfiguration, or prevent deployments from functioning.
From the tool's definition Delete a Vercel environment variable by its env id (get ids from vercel_get_env). The word 'Delete' combined with the operation on configuration data indicates irreversible removal.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
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 4 parameters: env_id, api_key, team_id, project_id. Required: env_id, 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.
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 →