AI agents call vercel_delete_env_var to permanently remove resources in Vercel — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting environment variables is an irreversible action that removes configuration from a Vercel project. This cannot be undone automatically and could break application functionality if critical variables are removed. While not directly dangerous like code deletion, it meets the Destructive category criteria as it irreversibly removes data.
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete an environment variable'. Environment variables are configuration data that cannot be trivially recovered once deleted.
Documented attack patterns abuse exactly the kind of access vercel_delete_env_var gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vercel, and nothing reaches the server without passing your rules. This is the rule we recommend for vercel_delete_env_var:
{
"version": "1",
"default": "deny",
"hide": [
"vercel_delete_env_var"
]
} vercel_delete_env_var 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.
Delete an environment variable. It is categorised as a Destructive tool in the Vercel MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vercel MCP server in PolicyLayer and add a rule for vercel_delete_env_var: 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 Vercel. Nothing to install.
vercel_delete_env_var 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_var 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_var. 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_var is provided by the Vercel MCP server (xiayeai/vercel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vercel, 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.
13 Vercel tools catalogued and risk-classified — across an index of 43,000+ MCP servers.