# get_env

A read tool on the ChukMCPServer MCP server.

Agent View of the PolicyLayer registry record for `get_env`. HTML page: https://policylayer.com/tools/ibm-chuk-mcp-server/get-env

## Facts

- Tool: `get_env`
- Server: ChukMCPServer (`ibm/chuk-mcp-server`) — https://policylayer.com/tools/ibm-chuk-mcp-server.md
- Homepage: https://github.com/IBM/chuk-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_env",
    "arguments": {}
  }
}
```

## Why get_env is rated Low

The tool retrieves environment variable data without side effects, fitting the Read category. Severity is medium rather than low because environment variables may contain sensitive information (API keys, credentials, configuration secrets) that could be misused if exposed to an untrusted agent, but the tool itself performs no destructive or financial operations.

From the tool's own definition: "Tool name 'get_env' indicates retrieval of environment variables; no description provided to suggest modification or execution capabilities."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches ChukMCPServer:

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

## Other tools on ChukMCPServer (12)

- `multiply` — Execute — https://policylayer.com/tools/ibm-chuk-mcp-server/multiply.md
- `add` — Other — https://policylayer.com/tools/ibm-chuk-mcp-server/add.md
- `advanced_tool` — Other — https://policylayer.com/tools/ibm-chuk-mcp-server/advanced-tool.md
- `bench_add` — Other — https://policylayer.com/tools/ibm-chuk-mcp-server/bench-add.md
- `bench_echo` — Other — https://policylayer.com/tools/ibm-chuk-mcp-server/bench-echo.md
- `echo` — Other — https://policylayer.com/tools/ibm-chuk-mcp-server/echo.md
- `hello` — Other — https://policylayer.com/tools/ibm-chuk-mcp-server/hello.md
- `hello_azure` — Other — https://policylayer.com/tools/ibm-chuk-mcp-server/hello-azure.md
- `hello_gcf` — Other — https://policylayer.com/tools/ibm-chuk-mcp-server/hello-gcf.md
- `hello_lambda` — Other — https://policylayer.com/tools/ibm-chuk-mcp-server/hello-lambda.md
- `universal_tool` — Other — https://policylayer.com/tools/ibm-chuk-mcp-server/universal-tool.md
- `safe_lookup` — Read — https://policylayer.com/tools/ibm-chuk-mcp-server/safe-lookup.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=ibm-chuk-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ibm-chuk-mcp-server