Saves external port configuration for a MySQL database in Dokploy.
AI agents use mysql-saveExternalPort 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.
This tool creates or modifies configuration settings (external port mapping) for a MySQL database. While it changes infrastructure configuration rather than data within the database, it is reversible through subsequent configuration updates.
From the tool's definition Tool name contains 'save' and description states 'Saves external port configuration', indicating a modification operation that persists configuration changes to a MySQL database service.
Attacks that exploit this kind of access
Saves external port configuration 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.
Register the Dokploy MCP Server MCP server in PolicyLayer and add a rule for mysql-saveExternalPort: 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.
mysql-saveExternalPort is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mysql-saveExternalPort 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.
Set action: deny in the PolicyLayer policy for mysql-saveExternalPort. 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.
mysql-saveExternalPort 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →