AI agents call int_delete 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.
This tool permanently removes an integration configuration without the ability to undo the action. While not affecting live deployments directly, deletion of integration configurations can break workflows and disable critical connections to third-party services. This qualifies as Destructive (irreversible data removal) rather than Write (reversible modification).
From the tool's definition Tool name 'int_delete' and description 'Delete an integration configuration' indicate irreversible deletion of data. Integration configurations are substantive configuration objects that cannot be recovered once removed.
Documented attack patterns abuse exactly the kind of access int_delete 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 int_delete:
{
"version": "1",
"default": "deny",
"hide": [
"int_delete"
]
}int_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an integration configuration. 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.
Register the Vercel MCP Server MCP server in PolicyLayer and add a rule for int_delete: 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.
int_delete 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 int_delete 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 int_delete. 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.
int_delete 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.
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.