update_service_env · Coolify MCP Tools MCP: Risk & Policy

WHAT IT DOES

What update_service_env does on Coolify MCP Tools

AI agents use update_service_env 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 update_service_env needs a policy

This tool modifies service configuration reversibly (environment variables can be changed back), placing it in the Write category rather than Execute or Destructive. Severity is high because environment variable changes can significantly impact service behavior, security posture, or integration with external systems.

From the tool's definition Tool name 'update_service_env' and description 'Update service environment variable' indicate modification of existing service configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_service_env Rate-limited

update_service_env 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": {
    "update_service_env": {
      "limits": [
        {
          "counter": "update_service_env_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 update_service_env

What does the update_service_env tool do? +

Update service environment variable. 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 update_service_env? +

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

What risk level is update_service_env? +

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

Can I rate-limit update_service_env? +

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

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

update_service_env 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.