Low Risk

env

Returns Go environment variables as structured JSON. Optionally request specific variables.

How to control env ↓

What env does on Make

AI agents call env to retrieve information from Make without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why env needs a policy

This tool queries and retrieves Go environment configuration without side effects. Environment variables are informational data that cannot be modified through a read operation. The optional parameter to request specific variables is still a query mechanism, not an action that creates, executes, or destroys anything. This is a straightforward Read category tool.

From the tool's definition Tool description states it 'Returns Go environment variables as structured JSON.' The verb 'Returns' and the read-only nature of retrieving environment variables (no modification, deletion, or execution) clearly indicate a retrieval operation.

Documented attack patterns abuse exactly the kind of access env gives an agent:

How to control env

PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for env:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "env": {}
  }
}

env is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Make — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about env

What does the env tool do? +

Returns Go environment variables as structured JSON. Optionally request specific variables. It is categorised as a Read tool in the Make MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on env? +

Register the Make MCP server in PolicyLayer and add a rule for 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 Make. Nothing to install.

What risk level is env? +

env is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit env? +

Yes. Add a rate_limit block to the 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.

How do I block env completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides env? +

env is provided by the Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Make tool call.

Start from Make, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.