set_env · LuzzyTool MCP: Risk & Policy

WHAT IT DOES

What set_env does on LuzzyTool

AI agents invoke set_env to trigger actions in LuzzyTool. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why set_env needs a policy

Setting environment variables that affect all subsequent shell command execution is an Execute-category action. It can be misused to hijack PATH, inject malicious library preloads (LD_PRELOAD), alter credentials, or influence security-sensitive configurations for every shell command run afterward — making it high severity due to the broad blast radius across the entire session.

From the tool's definition 设置临时环境变量，影响后续本会话中所有 shell 命令的执行环境 (sets temporary environment variables that affect the execution environment of all subsequent shell commands in the session)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_env Rate-limited

set_env stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_env": {
      "limits": [
        {
          "counter": "set_env_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches LuzzyTool, so you can run agents against it safely.

FAQ

Questions about set_env

What does the set_env tool do? +

【环境配置】在当前 MCP 会话中设置临时环境变量，影响后续本会话中所有 shell 命令的执行环境。. It is categorised as a Execute tool in the LuzzyTool MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on set_env? +

Register the LuzzyTool MCP server in PolicyLayer and add a rule for set_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 LuzzyTool. Nothing to install.

What risk level is set_env? +

set_env is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit set_env? +

Yes. Add a rate_limit block to the set_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 set_env completely? +

Set action: deny in the PolicyLayer policy for set_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 set_env? +

set_env is provided by the LuzzyTool MCP server (luzzymeow/luzzytool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.