// SCAN REPORT

Dokploy

50 tools. 30 can modify or destroy data without limits.

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

Last updated: 3 Jul 2026

30 can modify or destroy data

20 read-only

50 tools total

Community server · catalogue entry verified 03/07/2026

How to control Dokploy ↓

TOOL MAP

What Dokploy exposes to your agents

Read (20) Write / Execute (27) Destructive / Financial (3)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Dokploy tools

Destructive · High dokploy_delete_environment Deleting environment variables can break application functionality and cannot be easily undone, as the variables are permanently removed. Destructive · High dokploy_remove_backup This tool permanently removes backup configurations, which cannot be undone. Destructive · High dokploy_remove_volume_backup This tool permanently deletes a volume backup configuration, which cannot be undone. Execute · High dokploy_cancel_deployment Cancelling a running deployment is an operational action that interrupts an in-progress process and affects application availability.

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

POLICY

How to control Dokploy

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

Deny destructive operations

{
  "dokploy_delete_environment": {
    "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

{
  "dokploy_create_application": {
    "limits": [
      {
        "counter": "dokploy_create_application_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "dokploy_get_app_monitoring": {
    "limits": [
      {
        "counter": "dokploy_get_app_monitoring_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

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

ENFORCE POLICY ON DOKPLOY →

Instant setup, no code required.

FULL CATALOGUE

All 50 Dokploy tools

DESTRUCTIVE 3 tools

Destructive dokploy_delete_environment Remove environment variables from an application by key name. Destructive dokploy_remove_backup Delete a backup configuration. Does not delete previously created backup files at the destination. Destructive dokploy_remove_volume_backup Delete a volume backup configuration. Does not delete previously created backup files at the destination.

EXECUTE 12 tools

Execute dokploy_cancel_deployment Cancel a running deployment for an application. Execute dokploy_deploy Trigger a deployment for an application. Execute dokploy_deploy_compose Deploy a compose stack. Execute dokploy_kill_build Kill a stuck or hung build for an application. Execute dokploy_redeploy_application Rebuild and redeploy an application from its existing source. Execute dokploy_redeploy_compose Redeploy a compose stack from existing source. Execute dokploy_start_application Start a stopped application. Execute dokploy_start_compose Start a stopped compose stack. Execute dokploy_stop_application Stop a running application. Execute dokploy_stop_compose Stop a running compose stack. Execute dokploy_trigger_compose_backup Run a compose backup now, ignoring its schedule. Execute dokploy_trigger_volume_backup Run a volume backup now, ignoring its schedule.

WRITE 15 tools

Write dokploy_create_application Create a new application within an environment. Git/build provider config (GitHub, Dockerfile, etc.) is set vi Write dokploy_create_application_volume_backup Create a scheduled volume backup for an application. The named Docker volume is uploaded to the backup destina Write dokploy_create_compose Create a new compose stack within an environment. The compose file contents and git/source config can be set v Write dokploy_create_compose_backup Create a scheduled backup for a database running inside a compose stack. databaseType selects which DB inside Write dokploy_create_compose_volume_backup Create a scheduled volume backup for a service inside a compose stack. serviceName identifies which service in Write dokploy_create_domain Add a domain to an application. Write dokploy_create_environment Create a new environment within an existing project. Write dokploy_create_project Create a new project. A default Write dokploy_save_build_type Update build configuration for an application. All fields are required (pass empty string for unused fields). Write dokploy_save_github_provider Update GitHub source configuration for an application. Write dokploy_update_application Update application config fields. Only applicationId is required; all other fields are optional. Supports: nam Write dokploy_update_backup Update a backup configuration. Dokploy Write dokploy_update_compose Update compose stack config fields. Only composeId is required; all other fields are optional. Write dokploy_update_environment Set environment variables for an application. Merges with existing vars (existing keys are overwritten, new ke Write dokploy_update_volume_backup Update a volume backup configuration. Fetch the current config with dokploy_get_volume_backup first, then send

READ 20 tools

Read dokploy_get_app_monitoring Get CPU and memory metrics for an application by its appName. Read dokploy_get_application Get application config by ID. Returns status, git provider config, and other fields. Environment variables and Read dokploy_get_backup Get a backup configuration by ID, including its destination and linked service. Read dokploy_get_compose Get compose stack config by ID. Read dokploy_get_containers List all Docker containers. Optionally filter by server ID. Read dokploy_get_version Get the current Dokploy server version. Read dokploy_get_volume_backup Get a volume backup configuration by ID, including its destination and linked service. Read dokploy_list_applications List all applications across all projects and environments. Returns each application with its projectName and Read dokploy_list_backup_files List backup files at a destination. search is a path-or-prefix inside the bucket; pass an empty string for the Read dokploy_list_compose_deployments List deployments for a compose stack (newest first). Read dokploy_list_compose_domains List domains configured for a compose stack. Read dokploy_list_compose_services List services defined in a compose stack. Read dokploy_list_deployments List deployments for an application (newest first). Returns status, logPath, startedAt, finishedAt, and errorM Read dokploy_list_destinations List all configured S3-compatible backup destinations. Use this to find a destinationId for creating backups. Read dokploy_list_domains List all domains configured for an application. Read dokploy_list_environment List environment variables, build args, and build secrets for an application. Read dokploy_list_instances List all configured Dokploy instances. Returns instance names and URLs. Use this to discover valid instance na Read dokploy_list_projects List all projects in Dokploy Read dokploy_list_servers List all servers registered in Dokploy. Read dokploy_list_volume_backups List volume backups attached to a service. Pass the service ID and its type (

EXPLORE

Related servers

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

FAQ

Questions about Dokploy

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

Yes. The Dokploy server exposes 3 destructive tools including dokploy_delete_environment, dokploy_remove_backup, dokploy_remove_volume_backup. 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? +

The Dokploy server has 15 write tools including dokploy_create_application, dokploy_create_application_volume_backup, dokploy_create_compose. 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.

How many tools does the Dokploy MCP server expose? +

50 tools across 4 categories: Destructive, Execute, Read, Write. 20 are read-only. 30 can modify, create, or delete data.

How do I enforce a policy on Dokploy? +

Register the Dokploy 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 tool call.

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

ENFORCE POLICY ON DOKPLOY →

Instant setup, no code required.

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