vercel_create_deployment

SERVERUnClick SOURCE@unclick/mcp-server

High RISK CLASS

Category Execute

Parameters 120 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-deployment.md

WHAT IT DOES

What vercel_create_deployment does on UnClick

AI agents invoke vercel_create_deployment to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

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.

RISK

Why vercel_create_deployment is rated High

Triggers cloud deployments, executing builds and publishing services to external infrastructure.

From the tool's definition Create a Vercel preview deployment... deploy fresh from git

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

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Rate-limited

vercel_create_deployment stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vercel_create_deployment": {
      "limits": [
        {
          "counter": "vercel_create_deployment_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about vercel_create_deployment

What does the vercel_create_deployment tool do? +

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 Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does vercel_create_deployment accept? +

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.

How do I enforce a policy on vercel_create_deployment? +

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.

What risk level is vercel_create_deployment? +

vercel_create_deployment is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit vercel_create_deployment? +

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.

How do I block vercel_create_deployment completely? +

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.

What MCP server provides vercel_create_deployment? +

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.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools → High-risk tools on this server →

Across the catalogue

diagram_create on Templonix Lite MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →