mittwald_database_mysql_port_forward
Forward the TCP port of a MySQL database to a local port (provides command for long-running execution)
This record as markdown: /tools/mittwald-mcp-server/mittwald-database-mysql-port-forward.md
What mittwald_database_mysql_port_forward does on Mittwald MCP Server
AI agents invoke mittwald_database_mysql_port_forward to trigger actions in Mittwald MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why mittwald_database_mysql_port_forward is rated High
This tool executes a network port-forwarding command that creates a tunnel to a MySQL database, enabling direct TCP access. It runs an external CLI command and establishes a persistent network connection. Misuse could expose a database to unintended network access or allow exfiltration of sensitive data.
From the tool's definition Forward the TCP port of a MySQL database to a local port (provides command for long-running execution)
Attacks that exploit this kind of access
The rule that runs mittwald_database_mysql_port_forward safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mittwald MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mittwald_database_mysql_port_forward, this is the rule to start with:
mittwald_database_mysql_port_forward stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mittwald MCP Server, apply this rule, and every mittwald_database_mysql_port_forward call is checked against it from then on.
Questions about mittwald_database_mysql_port_forward
Forward the TCP port of a MySQL database to a local port (provides command for long-running execution). It is categorised as a Execute tool in the Mittwald MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mittwald MCP Server MCP server in PolicyLayer and add a rule for mittwald_database_mysql_port_forward: 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 Mittwald MCP Server. Nothing to install.
mittwald_database_mysql_port_forward is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mittwald_database_mysql_port_forward 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 mittwald_database_mysql_port_forward. 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.
mittwald_database_mysql_port_forward is provided by the Mittwald MCP Server MCP server (mittwald/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mittwald MCP Server, and thousands of servers like it.
Across the catalogue