Cancel a deployment
AI agents call vercel.deployment_cancel 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.
Cancelling a deployment stops an ongoing deployment operation in a way that cannot be undone. The deployment would need to be restarted from scratch, making this effectively irreversible. This falls under Destructive as it permanently terminates an operation, with high severity since it can disrupt production deployments or critical release pipelines.
From the tool's definition "Cancel a deployment" - cancelling a deployment is an irreversible action that terminates an in-progress deployment process
Attacks that exploit this kind of access
Cancel a deployment. 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.deployment_cancel: 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.deployment_cancel 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.deployment_cancel 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.deployment_cancel. 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.deployment_cancel 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 →