Show environment information including environment variables
AI agents call env to retrieve information from MCP Build Environment Service without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and displays environment configuration data. While environment variables can sometimes contain sensitive information (API keys, credentials), the tool itself performs a read-only inspection with no ability to modify, execute, or delete anything. The blast radius is limited to information disclosure risk, making this a low-severity Read operation.
From the tool's definition Tool name is 'env' and description states 'Show environment information including environment variables' — this is a query/inspection operation with no side effects.
Attacks that exploit this kind of access
Show environment information including environment variables. It is categorised as a Read tool in the MCP Build Environment Service MCP Server, which means it retrieves data without modifying state.
Register the MCP Build Environment Service 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 MCP Build Environment Service. Nothing to install.
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 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 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.
env is provided by the MCP Build Environment Service MCP server (jbroll/mcp-build). 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 →