vercel_create_deployment
Create a Vercel preview deployment. Direct production creation is disabled: production must use the canonical Safe Beta delivery rail with shared exact-SHA admission, staged smoke, promotion proof, and a terminal receipt. Pass deployment_id to redeploy an existing commit, or project_id + git_ref ...
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/vercel-create-deployment.md
What vercel_create_deployment does on UnClick
AI agents use vercel_create_deployment 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | |
gitRef | string | — | Alias for git_ref. |
target | string | — | Use 'preview'. 'production' is refused and must use the canonical delivery rail. |
teamId | string | — | Alias for team_id. |
api_key | string | — | |
git_ref | string | — | Branch or SHA to deploy. Defaults to 'main'. |
team_id | string | — | |
forceNew | boolean | — | Alias for force_new. |
force_new | boolean | — | Skip build cache. Default false. |
projectId | string | — | Alias for project_id. |
project_id | string | — | Deploy fresh from the project's linked git repo. |
deploymentId | string | — | Alias for deployment_id. |
Parameters from the server's own tool schema.
Why vercel_create_deployment is rated Medium
An AI agent can call vercel_create_deployment faster than any human can review: one bad instruction and it creates or modifies resources in UnClick by the hundred, each call as confident as the last.
Risk signalsHandles credentials or secrets (api_key) · High parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs vercel_create_deployment 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_create_deployment, this is the rule to start with:
vercel_create_deployment stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every vercel_create_deployment call is checked against it from then on.
Questions about vercel_create_deployment
Create a Vercel preview deployment. Direct production creation is disabled: production must use the canonical Safe Beta delivery rail with shared exact-SHA admission, staged smoke, promotion proof, and a terminal receipt. Pass deployment_id to redeploy an existing commit, or project_id + git_ref to deploy fresh from git. Set force_new=true to skip the build cache. 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.
vercel_create_deployment accepts 12 parameters: name, gitRef, target, teamId, api_key, git_ref, team_id, forceNew, force_new, projectId, project_id, deploymentId. 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_create_deployment: 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_create_deployment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vercel_create_deployment 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_create_deployment. 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_create_deployment 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.
This server
Across the catalogue