AI agents call vercel_projects to retrieve information from Access without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only listing operation returning project information. However, given that this is part of a credential store proxy (Access server) with per-agent permissioning, exposure of project structure and deployment status could enable reconnaissance for privilege escalation or attack planning against Vercel infrastructure.
From the tool's definition Tool description states 'List all Vercel projects' — a query operation that retrieves project metadata (names, frameworks, deployment status) with no modification or deletion of data.
Attacks that exploit this kind of access
List all Vercel projects in the account with their names, frameworks, and latest deployment status. Use this to get project IDs needed by vercel_deployments and vercel_env. It is categorised as a Read tool in the Access MCP Server, which means it retrieves data without modifying state.
Register the Access MCP server in PolicyLayer and add a rule for vercel_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 Access. Nothing to install.
vercel_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_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_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_projects is provided by the Access MCP server (scottpedia0/access). 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 →