mysql-saveEnvironment · Dokploy MCP Server MCP

WHAT IT DOES

What mysql-saveEnvironment does on Dokploy MCP Server

AI agents use mysql-saveEnvironment 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 mysql-saveEnvironment needs a policy

This tool modifies environment variables for a MySQL database, which is a reversible Write operation. However, the severity is elevated to 'high' because environment variables for database connections often contain sensitive credentials (passwords, connection strings) whose compromise could enable unauthorized database access, data exfiltration, or manipulation.

From the tool's definition Tool name includes 'save' and description states 'Saves environment variables for a MySQL database in Dokploy', indicating creation or modification of configuration data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mysql-saveEnvironment Rate-limited

mysql-saveEnvironment 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": {
    "mysql-saveEnvironment": {
      "limits": [
        {
          "counter": "mysql-saveenvironment_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 mysql-saveEnvironment

What does the mysql-saveEnvironment tool do? +

Saves environment variables for a MySQL database 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 mysql-saveEnvironment? +

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

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

Can I rate-limit mysql-saveEnvironment? +

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

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

mysql-saveEnvironment 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.