system_env_var
A read tool on the Container- MCP server.
This record as markdown: /tools/54rt1n-container-mcp/system-env-var.md
What system_env_var does on Container-MCP
AI agents call system_env_var to retrieve information from Container-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why system_env_var is rated Low
Environment variable retrieval is a read operation with minimal side effects. However, confidence is reduced due to empty description—the tool could potentially modify or expose sensitive data depending on implementation. The 'system_' prefix and sibling tools (fs_read, fs_write, etc.) suggest this server provides sandboxed operations, making accidental exposure less critical than in an unrestricted environment.
From the tool's definition Tool name 'system_env_var' suggests retrieval of environment variables; no description provided to indicate modification or execution.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs system_env_var safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Container-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For system_env_var, this is the rule to start with:
system_env_var 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 Container-MCP, apply this rule, and every system_env_var call is checked against it from then on.
Questions about system_env_var
system_env_var is a read tool on the Container MCP server. It is categorised as a Read tool in the Container-MCP MCP Server, which means it retrieves data without modifying state.
Register the Container MCP server in PolicyLayer and add a rule for system_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 Container-MCP. Nothing to install.
system_env_var 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 system_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 system_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.
system_env_var is provided by the Container MCP server (54rt1n/container-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Container, and thousands of servers like it.
This server
Across the catalogue