Critical Risk →

domain_remove

Remove a domain

How to control domain_remove ↓

AI agents call domain_remove to permanently remove resources in Vercel MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Removing a domain is a destructive operation that cannot be automatically undone. It permanently deletes domain routing configuration, potentially disrupting production traffic and breaking DNS records. While not directly causing data loss, it severs critical infrastructure bindings. The high severity reflects that an AI agent misusing this could take production domains offline, affecting service availability.

From the tool's definition Tool name 'domain_remove' with description 'Remove a domain' indicates irreversible deletion of a domain configuration from a Vercel project.

Documented attack patterns abuse exactly the kind of access domain_remove gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Vercel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for domain_remove:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "domain_remove"
  ]
}

domain_remove disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Vercel MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the domain_remove tool do? +

Remove a domain. It is categorised as a Destructive tool in the Vercel MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on domain_remove? +

Register the Vercel MCP Server MCP server in PolicyLayer and add a rule for domain_remove: 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 MCP Server. Nothing to install.

What risk level is domain_remove? +

domain_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit domain_remove? +

Yes. Add a rate_limit block to the domain_remove 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 domain_remove completely? +

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

domain_remove is provided by the Vercel MCP Server MCP server (quegenx/vercel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Vercel MCP Server tool call.

Deterministic rules across all 154 Vercel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

154 Vercel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.