Delete one or more blobs from Vercel Blob storage using their URLs.
AI agents call vercel-blob-delete to permanently remove resources in Mcp Gmail — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data from storage. Deletion operations cannot be undone and represent the most severe category (Destructive ranks above Execute, Write, and Read). The ability to delete multiple blobs via URLs creates significant blast radius if an AI agent is misdirected or compromised, potentially destroying critical application assets.
From the tool's definition Tool name 'vercel-blob-delete' and description 'Delete one or more blobs from Vercel Blob storage' explicitly indicate permanent deletion of data.
Attacks that exploit this kind of access
Delete one or more blobs from Vercel Blob storage using their URLs. It is categorised as a Destructive tool in the Mcp Gmail MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Gmail MCP server in PolicyLayer and add a rule for vercel-blob-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 Mcp Gmail. Nothing to install.
vercel-blob-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 vercel-blob-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 vercel-blob-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.
vercel-blob-delete is provided by the Mcp Gmail MCP server (@monsoft/mcp-gmail). 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 →