Dokploy MCP Server

67 tools. 54 can modify or destroy data without limits.

5 destructive tools with no built-in limits. Policy required.

Last updated:

54 can modify or destroy data
13 read-only
67 tools total

Community server · catalogue entry verified 03/07/2026

How to control Dokploy MCP Server ↓

What Dokploy MCP Server exposes to your agents

Read (13) Write / Execute (49) Destructive / Financial (5)
Critical Risk

The most dangerous Dokploy MCP Server tools

54 of Dokploy MCP Server's 67 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Dokploy MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Dokploy MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "application-delete": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "application-cleanQueues": {
    "limits": [
      {
        "counter": "application-cleanqueues_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "application-one": {
    "limits": [
      {
        "counter": "application-one_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Dokploy MCP Server — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON DOKPLOY →

Instant setup, no code required.

All 67 Dokploy MCP Server tools

WRITE 34 tools
Write application-cleanQueues Cleans the queues for an application in Dokploy. Write application-create Creates a new application in Dokploy. Write application-disconnectGitProvider Disconnects Git provider configuration from an application in Dokploy. Write application-markRunning Marks an application as running in Dokploy. Write application-move Moves an application to a different environment in Dokploy. Write application-refreshToken Refreshes the token for an application in Dokploy. Write application-saveBitbucketProvider Saves Bitbucket provider configuration for an application in Dokploy. Write application-saveBuildType Saves build type configuration for an application in Dokploy. Write application-saveDockerProvider Saves Docker provider configuration for an application in Dokploy. Write application-saveEnvironment Saves environment variables for an application in Dokploy. Write application-saveGiteaProvider Saves Gitea provider configuration for an application in Dokploy. Write application-saveGithubProvider Saves GitHub provider configuration for an application in Dokploy. Write application-saveGitlabProvider Saves GitLab provider configuration for an application in Dokploy. Write application-saveGitProvider Saves Git provider configuration for an application in Dokploy. Write application-update Updates an existing application in Dokploy. Write application-updateTraefikConfig Updates Traefik configuration for an application in Dokploy. Write domain-create Creates a new domain configuration in Dokploy. Domains can be configured for applications, compose services, o Write domain-update Updates an existing domain configuration in Dokploy. Allows modifying domain settings including host, SSL conf Write mysql-changeStatus Changes the status of a MySQL database in Dokploy. Write mysql-create Creates a new MySQL database in Dokploy. Write mysql-move Moves a MySQL database to a different environment in Dokploy. Write mysql-rebuild Rebuilds a MySQL database in Dokploy. Write mysql-saveEnvironment Saves environment variables for a MySQL database in Dokploy. Write mysql-saveExternalPort Saves external port configuration for a MySQL database in Dokploy. Write mysql-update Updates a MySQL database configuration in Dokploy. Write postgres-create Creates a new PostgreSQL database in Dokploy. Write postgres-move Moves a PostgreSQL database to a different environment in Dokploy. Write postgres-rebuild Rebuilds a PostgreSQL database in Dokploy. Write postgres-saveEnvironment Saves environment variables for a PostgreSQL database in Dokploy. Write postgres-saveExternalPort Saves external port configuration for a PostgreSQL database in Dokploy. Write postgres-update Updates an existing PostgreSQL database in Dokploy. Write project-create Creates a new project in Dokploy. Write project-duplicate Duplicates an existing environment in Dokploy with optional service selection. Creates a new environment with Write project-update Updates an existing project in Dokploy. Only provide the fields you want to update. System fields like created

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Dokploy MCP Server

Can an AI agent delete data through the Dokploy MCP Server MCP server? +

Yes. The Dokploy MCP Server server exposes 5 destructive tools including application-delete, domain-delete, mysql-remove. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Dokploy MCP Server? +

The Dokploy MCP Server server has 34 write tools including application-cleanQueues, application-create, application-disconnectGitProvider. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Dokploy MCP Server.

How many tools does the Dokploy MCP Server MCP server expose? +

67 tools across 4 categories: Destructive, Execute, Read, Write. 13 are read-only. 54 can modify, create, or delete data.

How do I enforce a policy on Dokploy MCP Server? +

Register the Dokploy MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Dokploy MCP Server tool call.

Deterministic rules across all 67 Dokploy MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

67 Dokploy MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Dokploy MCP Server's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.