AI agents use vercel-blob-put-file to create or update resources in Mcp Gmail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Gmail environment.
This tool performs a file upload to external cloud storage (Vercel Blob), which is a Write operation that creates or modifies data. While reversible (files can be overwritten or deleted separately), the upload itself creates new data artifacts.
From the tool's definition Tool description states 'Upload a file to Vercel Blob storage' and 'file will be read, converted to base64, and uploaded automatically.' The upload operation creates or modifies data in cloud storage.
Attacks that exploit this kind of access
Upload a file to Vercel Blob storage by providing the full file path. The file will be read, converted to base64, and uploaded automatically. It is categorised as a Write tool in the Mcp Gmail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Gmail MCP server in PolicyLayer and add a rule for vercel-blob-put-file: 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-put-file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vercel-blob-put-file 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-put-file. 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-put-file 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 →