List all Vercel projects with their latest deployment state.
AI agents call vercel_projects to retrieve information from Perceptdot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves project information and deployment metadata from Vercel. It performs a read-only query operation that returns data without creating, modifying, deleting, executing code, or performing financial transactions. The blast radius of misuse is minimal—an agent could only enumerate projects and view their deployment status, which is informational data retrieval.
From the tool's definition Tool name 'vercel_projects' and description 'List all Vercel projects with their latest deployment state' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List all Vercel projects with their latest deployment state. It is categorised as a Read tool in the Perceptdot MCP Server, which means it retrieves data without modifying state.
Register the Perceptdot 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 Perceptdot. 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 Perceptdot MCP server (perceptdot/percept). 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 →