AI agents call list_access_group_projects to retrieve information from Vercel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates projects associated with an access group. It performs no side effects, creates no resources, executes no code, and modifies no state. It is a pure data retrieval operation, fitting the 'Read' category. Severity is low because listing projects poses minimal risk; the blast radius of misuse is limited to information disclosure of existing project associations.
From the tool's definition Tool name is 'list_access_group_projects' and description states 'List projects of an access group' — a straightforward query operation with no modification, deletion, or execution.
Documented attack patterns abuse exactly the kind of access list_access_group_projects gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vercel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_access_group_projects:
{
"version": "1",
"default": "deny",
"tools": {
"list_access_group_projects": {}
}
}list_access_group_projects is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List projects of an access group. It is categorised as a Read tool in the Vercel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vercel MCP Server MCP server in PolicyLayer and add a rule for list_access_group_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 Vercel MCP Server. Nothing to install.
list_access_group_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 list_access_group_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 list_access_group_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.
list_access_group_projects is provided by the Vercel MCP Server MCP server (quegenx/vercel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 154 Vercel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
154 Vercel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.