create_application_env
Create an environment variable for an application.
This record as markdown: /tools/coolify/create-application-env.md
What create_application_env does on Coolify
AI agents use create_application_env to create or update resources in Coolify, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coolify environment.
Why create_application_env is rated Medium
Creating environment variables modifies application configuration but is reversible—they can be updated or removed. This fits the Write category rather than Execute, as the tool itself does not run code or trigger external operations; it only stores configuration.
From the tool's definition Tool name 'create_application_env' and description 'Create an environment variable for an application' indicate data creation. Environment variables are configuration data that can be modified or deleted later, making this a reversible write operation.
Attacks that exploit this kind of access
The rule that runs create_application_env safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Coolify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_application_env, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Coolify, apply this rule, and every create_application_env call is checked against it from then on.
Questions about create_application_env
Create an environment variable for an application. It is categorised as a Write tool in the Coolify MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Coolify 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. Nothing to install.
create_application_env is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
create_application_env is provided by the Coolify MCP server (coolify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Coolify, and thousands of servers like it.
This server
Across the catalogue