project-update · Dokploy MCP Server MCP: Risk & Policy

WHAT IT DOES

What project-update does on Dokploy MCP Server

AI agents use project-update to create or update resources in Dokploy MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dokploy MCP Server environment.

WHY IT NEEDS A POLICY

Why project-update needs a policy

The tool modifies existing project configuration data in a reversible manner (updates can be changed or reverted). This is a Write operation, not Destructive (no permanent deletion), not Execute (no arbitrary code execution), and not Financial. Severity is medium because misconfigured project updates could disrupt deployed services, but the changes are generally recoverable.

From the tool's definition Tool name is 'project-update' and description states it 'Updates an existing project in Dokploy' with instruction to 'Only provide the fields you want to update', indicating reversible modification of project data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

project-update Rate-limited

project-update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "project-update": {
      "limits": [
        {
          "counter": "project-update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Dokploy MCP Server, so you can run agents against it safely.

FAQ

Questions about project-update

What does the project-update tool do? +

Updates an existing project in Dokploy. Only provide the fields you want to update. System fields like createdAt and organizationId are typically not modified. It is categorised as a Write tool in the Dokploy MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on project-update? +

Register the Dokploy MCP Server MCP server in PolicyLayer and add a rule for project-update: 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 Dokploy MCP Server. Nothing to install.

What risk level is project-update? +

project-update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit project-update? +

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

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

project-update is provided by the Dokploy MCP Server MCP server (limehawk/dokploy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.