deploy_by_tag_or_uuid
Trigger a deployment by tag or UUID. Supports force deploy and pull-request deployments.
This record as markdown: /tools/coolify/deploy-by-tag-or-uuid.md
What deploy_by_tag_or_uuid does on Coolify
AI agents invoke deploy_by_tag_or_uuid to trigger actions in Coolify. 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 deploy_by_tag_or_uuid is rated High
This tool executes deployment operations on a Coolify-managed infrastructure. While not destructive by itself, deployments trigger external systems and code execution in production/staging environments. The 'force deploy' option and ability to deploy arbitrary tags/UUIDs amplify risk. Misuse could corrupt application state, expose secrets, or disrupt services.
From the tool's definition Tool name contains 'deploy' and description states 'Trigger a deployment', which initiates external operations (containerized application deployment) whose effects depend on arguments (tag, UUID, force flag, PR configuration).
Attacks that exploit this kind of access
The rule that runs deploy_by_tag_or_uuid 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 deploy_by_tag_or_uuid, this is the rule to start with:
deploy_by_tag_or_uuid 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Coolify, apply this rule, and every deploy_by_tag_or_uuid call is checked against it from then on.
Questions about deploy_by_tag_or_uuid
Trigger a deployment by tag or UUID. Supports force deploy and pull-request deployments. It is categorised as a Execute tool in the Coolify MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Coolify MCP server in PolicyLayer and add a rule for deploy_by_tag_or_uuid: 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.
deploy_by_tag_or_uuid is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the deploy_by_tag_or_uuid 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 deploy_by_tag_or_uuid. 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.
deploy_by_tag_or_uuid 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.
Across the catalogue