deploy_by_tag_or_uuid

Trigger a deployment by tag or UUID. Supports force deploy and pull-request deployments.

SERVERCoolify SOURCEcoolify-mcp-server
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about deploy_by_tag_or_uuid

What does the deploy_by_tag_or_uuid tool do? +

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.

How do I enforce a policy on deploy_by_tag_or_uuid? +

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.

What risk level is deploy_by_tag_or_uuid? +

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

Can I rate-limit deploy_by_tag_or_uuid? +

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.

How do I block deploy_by_tag_or_uuid completely? +

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.

What MCP server provides deploy_by_tag_or_uuid? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Coolify's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.