docker_network_alias · Coolify MCP: Risk & Policy

WHAT IT DOES

What docker_network_alias does on Coolify

AI agents invoke docker_network_alias to trigger actions in Coolify. 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 docker_network_alias needs a policy

This tool executes SSH commands to modify Docker container network aliases. While the action itself (adding a network alias) is technically reversible, it requires manual intervention and the alias is explicitly lost on container rebuild/redeploy. The tool's function is to trigger an external operation (SSH command execution) whose effects persist beyond the command execution.

From the tool's definition Generates SSH commands to add the friendly-name alias. Run after database create + start. The tool generates and presumably executes SSH commands, which are external operations with effects that depend on the alias name and target arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

docker_network_alias Rate-limited

docker_network_alias 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": {
    "docker_network_alias": {
      "limits": [
        {
          "counter": "docker_network_alias_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 Coolify, so you can run agents against it safely.

FAQ

Questions about docker_network_alias

What does the docker_network_alias tool do? +

Workaround for Coolify upstream bug: DB containers are aliased by UUID only, not by friendly name. Generates SSH commands to add the friendly-name alias. Run after database create + start. Warning: alias is lost on container rebuild/redeploy. It is categorised as a Execute tool in the Coolify MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on docker_network_alias? +

Register the Coolify MCP server in PolicyLayer and add a rule for docker_network_alias: 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 docker_network_alias? +

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

Can I rate-limit docker_network_alias? +

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

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

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