security.sanitizeEnv

MCP tool from Agent Rack by lakpriya1s

Strip env vars matching credential patterns before spawning agents (default true). Prefer per-agent inheritEnv.

How to use it

security.sanitizeEnv is exposed by the Agent Rack MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the security.sanitizeEnv tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.

Install Agent Rack

$npx agent-rack setup

FULL AGENT RACK LISTING

Other tools in Agent Rack (39)

adversarial

boolean

agent

string

agent_list_available

No parameters. Lists every configured agent and whether its binary is on $PATH.

agent_run

agent_session_cancel

agent_session_create

Same execution parameters as agentrun (agent, prompt required; workspace, mode,

agent-rack-review-handling

An agentreview call returns

agent-rack-tool-selection

Delegating any task to a sub-agent through agent-rack

agents

Map of agent id → { name, command, args, transport, env, description, model, inheritEnv }

allowedWorkspaces

Absolute directory paths agents may be launched in. Every tool call resolves symlinks and validates against this list before any subprocess spawns. See the caveat under Security model — this constrains the working directory, not everything the process can reach.

boolean

string

number

When transport is stdio (the default), also open a loopback SSE listener on the same session state, so agent-rack session status/tail and the dashboard can observe sessions created over the stdio connection with no separate server. Default true; same bearer-token protection as security.requireSseAut

string

Agents

number

/lineend may be 0 for whole-file, deleted-file, or architectural findings.

live

opencode

message

string