bulk_update_service_envs · Coolify MCP Tools MCP

WHAT IT DOES

What bulk_update_service_envs does on Coolify MCP Tools

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

WHY IT NEEDS A POLICY

Why bulk_update_service_envs needs a policy

This tool creates or modifies data (environment variables) at scale across services. While reversible (Write category), the bulk nature and potential to affect service behavior across multiple services elevates severity to high. It is not Execute (doesn't run commands), not Destructive (changes are reversible), not Financial, and not Read (modifies data).

From the tool's definition bulk_update_service_envs performs bulk update of service environment variables, modifying configuration data across potentially multiple services.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bulk_update_service_envs Rate-limited

bulk_update_service_envs 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_update_service_envs": {
      "limits": [
        {
          "counter": "bulk_update_service_envs_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 MCP Tools, so you can run agents against it safely.

FAQ

Questions about bulk_update_service_envs

What does the bulk_update_service_envs tool do? +

Bulk update service environment variables. It is categorised as a Write tool in the Coolify MCP Tools 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_update_service_envs? +

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

What risk level is bulk_update_service_envs? +

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

Can I rate-limit bulk_update_service_envs? +

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

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

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