This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/vercel-list-projects.md
What vercel_list_projects does on UnClick
AI agents call vercel_list_projects to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | |
teamId | string | — | |
api_key | string | — |
Parameters from the server's own tool schema.
Why vercel_list_projects is rated Low
This tool retrieves information about Vercel projects without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that lists existing projects, which is typical of query/fetch functionality. The severity is low because listing projects exposes metadata but not necessarily sensitive code or credentials, though it does reveal project inventory.
From the tool's definition Tool name 'vercel_list_projects' and description 'List all Vercel projects' indicate a query/retrieval operation with no modification or execution of code.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs vercel_list_projects safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vercel_list_projects, this is the rule to start with:
vercel_list_projects is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every vercel_list_projects call is checked against it from then on.
Questions about vercel_list_projects
List all Vercel projects. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
vercel_list_projects accepts 3 parameters: limit, teamId, api_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick 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 UnClick. 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 UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue