bulk_env_update · Coolify MCP: Risk & Policy

WHAT IT DOES

What bulk_env_update does on Coolify

AI agents use bulk_env_update to create or update resources in Coolify — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coolify environment.

WHY IT NEEDS A POLICY

Why bulk_env_update needs a policy

This tool creates or modifies configuration data (environment variables) across multiple applications in a reversible manner—a core Write operation. Severity is high because misconfigured environment variables can break applications, expose secrets, or cause service outages across multiple systems simultaneously. The bulk nature and cross-application scope amplify the blast radius of a mistaken or malicious update.

From the tool's definition Tool name 'bulk_env_update' and description 'Update env var across multiple apps' explicitly indicates modifying environment variables at scale across multiple applications.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bulk_env_update Rate-limited

bulk_env_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bulk_env_update": {
      "limits": [
        {
          "counter": "bulk_env_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about bulk_env_update

What does the bulk_env_update tool do? +

Update env var across multiple apps. It is categorised as a Write tool in the Coolify MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on bulk_env_update? +

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

What risk level is bulk_env_update? +

bulk_env_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit bulk_env_update? +

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

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

bulk_env_update is provided by the Coolify MCP server (jurislm/coolify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.