AI agents call delete_edge_config_tokens 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.
The tool irreversibly deletes Edge Config tokens, which are security-sensitive credentials. Once deleted, these tokens cannot be recovered and any applications or services relying on them will lose access. This is an irreversible operation affecting authentication infrastructure, making it Destructive rather than Write.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete Edge Config Tokens'. Edge Config tokens are authentication credentials used to access edge configuration in Vercel deployments.
Documented attack patterns abuse exactly the kind of access delete_edge_config_tokens 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 delete_edge_config_tokens:
{
"version": "1",
"default": "deny",
"hide": [
"delete_edge_config_tokens"
]
}delete_edge_config_tokens 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 Edge Config Tokens. 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 delete_edge_config_tokens: 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.
delete_edge_config_tokens 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 delete_edge_config_tokens 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 delete_edge_config_tokens. 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.
delete_edge_config_tokens 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.