vercel_list_projects
AI agents call vercel_list_projects to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a list of projects from Vercel without modifying, deleting, or executing operations. It is a read-only operation with minimal blast radius—an AI agent listing projects cannot cause harm beyond potential exposure of project names/metadata. The absence of a description lowers confidence slightly, but the naming pattern is sufficiently clear to categorize confidently as Read.
From the tool's definition Tool name 'vercel_list_projects' contains the verb 'list', which indicates data retrieval. The description is empty, but the naming convention is clear: 'list' operations are non-mutating queries that retrieve project information from Vercel.
Attacks that exploit this kind of access
vercel_list_projects. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for vercel_list_projects: 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 Integrations MCP. Nothing to install.
vercel_list_projects 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_projects 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_projects. 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_projects is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). 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 →