Remove domain from project
AI agents call vercel.domain_remove to permanently remove resources in MCP Fullstack — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a domain from a project is an irreversible action that cannot be undone without manual re-addition. This constitutes a destructive operation affecting infrastructure configuration. While not deleting data directly, it removes a critical resource binding.
From the tool's definition Tool name includes 'remove' and description states 'Remove domain from project' — indicating irreversible deletion of a domain association.
Attacks that exploit this kind of access
Remove domain from project. It is categorised as a Destructive tool in the MCP Fullstack MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Fullstack MCP server in PolicyLayer and add a rule for vercel.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 MCP Fullstack. Nothing to install.
vercel.domain_remove 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.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.
Set action: deny in the PolicyLayer policy for vercel.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.
vercel.domain_remove is provided by the MCP Fullstack MCP server (jacobfv/mcp-fullstack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →