vercel_get_env
Get environment variables for a Vercel project.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/vercel-get-env.md
What vercel_get_env does on UnClick
AI agents call vercel_get_env 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 |
|---|---|---|---|
teamId | string | — | Alias for team_id. |
api_key | string | — | |
decrypt | boolean | — | |
team_id | string | — | |
projectId | string | — | Alias for project_id. |
project_id | string | Yes |
Parameters from the server's own tool schema.
Why vercel_get_env is rated Low
This tool retrieves environment variables from a Vercel project. Environment variables often contain sensitive data such as API keys, database credentials, and secrets. While the operation itself is read-only (no side effects), the exposure of such secrets could facilitate further attacks.
From the tool's definition Tool name includes 'get' and description states 'Get environment variables' — a retrieval operation with no modification or deletion.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs vercel_get_env 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_get_env, this is the rule to start with:
vercel_get_env 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_get_env call is checked against it from then on.
Questions about vercel_get_env
Get environment variables for a Vercel project. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
vercel_get_env accepts 6 parameters: teamId, api_key, decrypt, team_id, projectId, project_id. Required: project_id. 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_get_env: 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_get_env 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_get_env 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_get_env. 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_get_env 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