application-saveGitProvider · Dokploy MCP Server MCP

WHAT IT DOES

What application-saveGitProvider does on Dokploy MCP Server

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

The tool modifies application configuration by saving Git provider settings. This is reversible (configuration can be updated again), so it falls under Write rather than Destructive. However, it has high severity because misconfiguration of Git providers could redirect deployments to malicious repositories, inject supply chain compromises, or break CI/CD pipelines.

From the tool's definition Tool name contains 'save' and description states 'Saves Git provider configuration for an application' — this is a create or modify operation that persists configuration data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

application-saveGitProvider Rate-limited

application-saveGitProvider 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-saveGitProvider": {
      "limits": [
        {
          "counter": "application-savegitprovider_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-saveGitProvider

What does the application-saveGitProvider tool do? +

Saves Git 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-saveGitProvider? +

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

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

Can I rate-limit application-saveGitProvider? +

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

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

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