mysql_router_route_connections
List active connections on a route including source/destination addresses, bytes transferred, and connection times.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-router-route-connections.md
What mysql_router_route_connections does on Mysql Mcp
AI agents call mysql_router_route_connections to retrieve information from Mysql Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mysql_router_route_connections is rated Low
This tool retrieves and displays diagnostic information about existing router connections. It performs read-only queries against connection metadata with no side effects, no code execution, and no data modification. The blast radius of misuse is minimal—an attacker gains visibility into connection patterns but cannot alter systems or access data beyond routing metadata.
From the tool's definition Tool description explicitly states it 'List[s] active connections' with information about 'source/destination addresses, bytes transferred, and connection times' - purely observational/diagnostic metadata with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs mysql_router_route_connections safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql_router_route_connections, this is the rule to start with:
mysql_router_route_connections is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mysql Mcp, apply this rule, and every mysql_router_route_connections call is checked against it from then on.
Questions about mysql_router_route_connections
List active connections on a route including source/destination addresses, bytes transferred, and connection times. It is categorised as a Read tool in the Mysql Mcp MCP Server, which means it retrieves data without modifying state.
Register the Mysql MCP server in PolicyLayer and add a rule for mysql_router_route_connections: 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 Mysql Mcp. Nothing to install.
mysql_router_route_connections is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mysql_router_route_connections 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_router_route_connections. 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_router_route_connections is provided by the Mysql MCP server (oci:docker.io/writenotenow/mysql-mcp:v1.0.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mysql, and thousands of servers like it.
This server
Across the catalogue