update_application_env · Coolify MCP Server MCP

WHAT IT DOES

What update_application_env does on Coolify MCP Server

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

This tool creates or modifies data (environment variables) reversibly—changes can be undone by updating again. It does not delete, execute arbitrary code, or move money. However, severity is high because misconfigured environment variables (e.g., database credentials, API keys, feature flags) can compromise application security, cause outages, or expose sensitive data.

From the tool's definition Tool name 'update_application_env' and description 'Update an environment variable for an application' indicate modification of application configuration data. Environment variables control runtime behavior, dependencies, and integration settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_application_env Rate-limited

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

FAQ

Questions about update_application_env

What does the update_application_env tool do? +

Update an environment variable for an application. 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 update_application_env? +

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

What risk level is update_application_env? +

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

Can I rate-limit update_application_env? +

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

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

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