List environment variables
AI agents call vercel.env_list to retrieve information from MCP Fullstack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads environment variable metadata from a Vercel deployment. While environment variables can contain sensitive information (secrets, API keys), the tool itself performs a non-destructive read operation with no side effects. The severity is low because: (1) listing does not expose values (only names), and (2) access control should restrict who can use this tool.
From the tool's definition 'List environment variables' - a query operation that retrieves configuration data without modification.
Attacks that exploit this kind of access
List environment variables. It is categorised as a Read tool in the MCP Fullstack MCP Server, which means it retrieves data without modifying state.
Register the MCP Fullstack MCP server in PolicyLayer and add a rule for vercel.env_list: 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 MCP Fullstack. Nothing to install.
vercel.env_list 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.env_list 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.env_list. 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.env_list is provided by the MCP Fullstack MCP server (jacobfv/mcp-fullstack). 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 →