New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

vercel_create_env

Create (or upsert) an environment variable on a Vercel project. Target defaults to production, preview, and development. Use type='plain' for non-secret values, 'encrypted' or 'sensitive' for secrets.

SERVERUnClick SOURCE@unclick/mcp-server
Medium RISK CLASS
Category Write
Parameters 122 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/vercel-create-env.md

What vercel_create_env does on UnClick

AI agents use vercel_create_env to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.

ParameterTypeRequiredDescription
key string Yes
type string plain | encrypted | sensitive | secret | system. Defaults to plain.
value string Yes
target string CSV of environments: 'production,preview,development'. Defaults to all three.
teamId string Alias for team_id.
upsert boolean Overwrite existing value for same key/target. Default true.
api_key string
comment string
team_id string
gitBranch string Alias for git_branch.
projectId string Alias for project_id.
git_branch string

Parameters from the server's own tool schema.

Why vercel_create_env is rated Medium

This tool modifies environment variables on a Vercel project, which are configuration values that can be changed or removed. While environment variables control application behavior and secrets management (elevating severity), the action itself is reversible—variables can be updated or deleted. This is Write rather than Execute because it doesn't run code or trigger operations; it configures them.

From the tool's definition Tool description explicitly states 'Create (or upsert) an environment variable' and provides options for sensitive/encrypted values. The word 'Create' and 'upsert' indicate reversible modification of configuration data.

Risk signalsHandles credentials or secrets (api_key) · High parameter count (13 properties)

Questions about vercel_create_env

What does the vercel_create_env tool do? +

Create (or upsert) an environment variable on a Vercel project. Target defaults to production, preview, and development. Use type='plain' for non-secret values, 'encrypted' or 'sensitive' for secrets. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does vercel_create_env accept? +

vercel_create_env accepts 12 parameters: key, type, value, target, teamId, upsert, api_key, comment, team_id, gitBranch, projectId, git_branch. Required: key, value. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on vercel_create_env? +

Register the UnClick MCP server in PolicyLayer and add a rule for vercel_create_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.

What risk level is vercel_create_env? +

vercel_create_env is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit vercel_create_env? +

Yes. Add a rate_limit block to the vercel_create_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.

How do I block vercel_create_env completely? +

Set action: deny in the PolicyLayer policy for vercel_create_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.

What MCP server provides vercel_create_env? +

vercel_create_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of UnClick's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.