AI agents call vercel_list_deployments to retrieve information from VibeServe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query/retrieval operation against Vercel's deployment history. It has no side effects, does not execute code, does not modify data, and does not delete or move resources. The blast radius of misuse is minimal—an agent could retrieve deployment information it shouldn't see, but cannot cause operational damage. Classified as Read with low severity.
From the tool's definition Tool name 'vercel_list_deployments' and description 'List Vercel deployments' indicate a read-only operation that retrieves deployment information without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
List Vercel deployments. It is categorised as a Read tool in the VibeServe MCP Server, which means it retrieves data without modifying state.
Register the VibeServe 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 VibeServe. 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 VibeServe MCP server (ncsound919/vibeserve). 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 →