List deployments for a project or all projects
AI agents call vercel_list_deployments to retrieve information from Vercel without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves deployment information; it does not create, modify, delete, or execute any operations. It has no ability to change state or trigger actions, making it a straightforward read operation with minimal risk. The severity is low because listing deployments exposes metadata that is typically not sensitive in isolation, though it could inform further attacks.
From the tool's definition Tool name is 'vercel_list_deployments' and description states 'List deployments for a project or all projects'. The verb 'list' is a classic read operation that retrieves and queries data without side effects.
Documented attack patterns abuse exactly the kind of access vercel_list_deployments gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vercel, and nothing reaches the server without passing your rules. This is the rule we recommend for vercel_list_deployments:
{
"version": "1",
"default": "deny",
"tools": {
"vercel_list_deployments": {}
}
} vercel_list_deployments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List deployments for a project or all projects. It is categorised as a Read tool in the Vercel MCP Server, which means it retrieves data without modifying state.
Register the Vercel MCP server in PolicyLayer and add a rule for vercel_list_deployments: 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. Nothing to install.
vercel_list_deployments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the vercel_list_deployments 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_list_deployments. 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_list_deployments is provided by the Vercel MCP server (xiayeai/vercel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vercel, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Vercel tools catalogued and risk-classified — across an index of 43,000+ MCP servers.