application-saveGitlabProvider · Dokploy MCP Server MCP

WHAT IT DOES

What application-saveGitlabProvider does on Dokploy MCP Server

AI agents use application-saveGitlabProvider 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 application-saveGitlabProvider needs a policy

This tool writes authentication and integration configuration (GitLab provider credentials) to Dokploy, enabling subsequent deployments and CI/CD operations. While reversible via updates, misuse could compromise CI/CD pipelines, enable unauthorized deployments, or expose sensitive credentials. The 'save' operation is a Write action (modifying application configuration state).

From the tool's definition Tool name contains 'save' and description states it 'Saves GitLab provider configuration for an application' — this creates or modifies provider credentials/configuration data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

application-saveGitlabProvider Rate-limited

application-saveGitlabProvider 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": {
    "application-saveGitlabProvider": {
      "limits": [
        {
          "counter": "application-savegitlabprovider_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 application-saveGitlabProvider

What does the application-saveGitlabProvider tool do? +

Saves GitLab provider configuration for an application in Dokploy. 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 application-saveGitlabProvider? +

Register the Dokploy MCP Server MCP server in PolicyLayer and add a rule for application-saveGitlabProvider: 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 application-saveGitlabProvider? +

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

Can I rate-limit application-saveGitlabProvider? +

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

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

application-saveGitlabProvider 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.