render_set_env_var
Set an environment variable on a Render service.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/render-set-env-var.md
What render_set_env_var does on UnClick
AI agents use render_set_env_var to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | Yes | Environment variable name |
value | string | Yes | Environment variable value |
api_key | string | — | |
service_id | string | Yes |
Parameters from the server's own tool schema.
Why render_set_env_var is rated Medium
This tool modifies configuration of a live Render service by setting environment variables. While technically a write operation (reversible in principle), environment variable changes can have significant security implications — exposing secrets, altering application behavior, or enabling privilege escalation — making the blast radius high.
From the tool's definition 'Set an environment variable on a Render service'
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs render_set_env_var 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 render_set_env_var, this is the rule to start with:
render_set_env_var stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 render_set_env_var call is checked against it from then on.
Questions about render_set_env_var
Set an environment variable on a Render service. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
render_set_env_var accepts 4 parameters: key, value, api_key, service_id. Required: key, value, service_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 render_set_env_var: 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.
render_set_env_var is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the render_set_env_var 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 render_set_env_var. 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.
render_set_env_var 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