This record as markdown: /tools/cowork-os/get-env.md
What get_env does on CoWork OS
AI agents call get_env to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_env is rated Low
This tool retrieves environment variable values without creating, modifying, or deleting data. It is a simple query operation that has no side effects. Severity is low because environment variables typically contain configuration data, though sensitive values (API keys, credentials) could theoretically be exposed—however, the tool itself is read-only and any risk depends entirely on what is stored in the environment…
From the tool's definition Tool description: 'Get the value of an environment variable'. The verb 'get' and the action of retrieving a value with no modification indicates a read-only operation.
Attacks that exploit this kind of access
The rule that runs get_env safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_env, this is the rule to start with:
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 CoWork OS, apply this rule, and every get_env call is checked against it from then on.
Questions about get_env
Get the value of an environment variable. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.
Register the CoWork OS MCP server in PolicyLayer and add a rule for 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 CoWork OS. Nothing to install.
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 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 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.
get_env is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue