execute_application_command · Coolify MCP Tools MCP

WHAT IT DOES

What execute_application_command does on Coolify MCP Tools

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

This tool runs arbitrary commands inside an application container, which is a classic Execute category action. The blast radius is high because malicious commands could compromise the containerized application, access sensitive data, modify application state, or pivot to other infrastructure.

From the tool's definition Tool name is 'execute_application_command' with description 'Execute a command in application container'. The verb 'Execute' and 'command in application container' directly indicate code execution within a containerized environment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_application_command Rate-limited

execute_application_command 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": {
    "execute_application_command": {
      "limits": [
        {
          "counter": "execute_application_command_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 MCP Tools, so you can run agents against it safely.

FAQ

Questions about execute_application_command

What does the execute_application_command tool do? +

Execute a command in application container. It is categorised as a Execute tool in the Coolify MCP Tools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_application_command? +

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

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

Can I rate-limit execute_application_command? +

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

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

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