create_service_env · Coolify MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_service_env does on Coolify MCP Server

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

WHY IT NEEDS A POLICY

Why create_service_env needs a policy

This tool creates (writes) environment variable configurations for services. While reversible (environment variables can be deleted or updated), it is high severity because environment variables often contain secrets, credentials, and sensitive configuration data. Misuse could allow an AI agent to inject malicious credentials, API keys, or configuration that compromises service security or operation.

From the tool's definition Tool name 'create_service_env' and description 'Create an environment variable for a service' indicate creation of configuration data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_service_env Rate-limited

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

FAQ

Questions about create_service_env

What does the create_service_env tool do? +

Create an environment variable for a service. It is categorised as a Write tool in the Coolify MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_service_env? +

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

What risk level is create_service_env? +

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

Can I rate-limit create_service_env? +

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

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

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