get_env

Read environment variables with automatic secret masking. Secrets (tokens, passwords, keys) are shown as masked values like

SERVERTerminal Guardian SOURCE7majesty-m/terminal-guardian-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/7majesty-m-terminal-guardian-mcp/get-env.md

WHAT IT DOES

What get_env does on Terminal Guardian

AI agents call get_env to retrieve information from Terminal Guardian without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_env is rated Low

This tool retrieves environment variable data without creating, modifying, or deleting anything. It performs a read-only query operation. However, severity is medium rather than low because environment variables may contain sensitive information (API keys, credentials, configuration) that could be exposed if the masking function fails or is bypassed, and an AI agent could inadvertently leak this data in its…

From the tool's definition Tool name 'get_env' and description 'Read environment variables with automatic secret masking' indicates data retrieval with no modification capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_env safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Terminal Guardian, 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 Allowed

get_env is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_env": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Terminal Guardian, apply this rule, and every get_env call is checked against it from then on.

FAQ

Questions about get_env

What does the get_env tool do? +

Read environment variables with automatic secret masking. Secrets (tokens, passwords, keys) are shown as masked values like. It is categorised as a Read tool in the Terminal Guardian MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_env? +

Register the Terminal Guardian 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 Terminal Guardian. Nothing to install.

What risk level is get_env? +

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

Can I rate-limit get_env? +

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.

How do I block get_env completely? +

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.

What MCP server provides get_env? +

get_env is provided by the Terminal Guardian MCP server (7majesty-m/terminal-guardian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Terminal Guardian, and thousands of servers like it.

This server

All 25 Terminal Guardian tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →