dokploy_save_github_provider · Dokploy MCP: Risk & Policy

WHAT IT DOES

What dokploy_save_github_provider does on Dokploy

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

WHY IT NEEDS A POLICY

Why dokploy_save_github_provider needs a policy

The tool updates (modifies) GitHub provider configuration for an application, which is a Write operation—it changes application settings but does not delete data or execute deployments. However, the severity is high because misconfiguring GitHub source settings could disrupt deployments, affect application access to repositories, or introduce security issues like credential exposure.

From the tool's definition Tool name contains 'save' and description states 'Update GitHub source configuration for an application.' This modifies existing configuration reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dokploy_save_github_provider Rate-limited

dokploy_save_github_provider 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": {
    "dokploy_save_github_provider": {
      "limits": [
        {
          "counter": "dokploy_save_github_provider_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, so you can run agents against it safely.

FAQ

Questions about dokploy_save_github_provider

What does the dokploy_save_github_provider tool do? +

Update GitHub source configuration for an application. It is categorised as a Write tool in the Dokploy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on dokploy_save_github_provider? +

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

What risk level is dokploy_save_github_provider? +

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

Can I rate-limit dokploy_save_github_provider? +

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

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

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