create_application_env · Coolify MCP Tools MCP

WHAT IT DOES

What create_application_env does on Coolify MCP Tools

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

This tool creates (writes) environment variables for applications, which are configuration data that can be modified reversibly. It does not execute code, delete data irreversibly, or move money. The severity is medium because misuse could inject sensitive values (API keys, secrets) into applications or alter runtime behavior in unintended ways, but the action is reversible (variables can be deleted or updated).

From the tool's definition Tool name is 'create_application_env' and description states 'Create application environment variable' — explicitly a creation operation that modifies application configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_application_env Rate-limited

create_application_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_application_env": {
      "limits": [
        {
          "counter": "create_application_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 create_application_env

What does the create_application_env tool do? +

Create application 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 create_application_env? +

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

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

Can I rate-limit create_application_env? +

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

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

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