mysql_router_route_destinations
List backend MySQL server destinations for a route. Shows address and port of each destination server.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-router-route-destinations.md
What mysql_router_route_destinations does on Mysql Mcp
AI agents call mysql_router_route_destinations 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_destinations is rated Low
This tool retrieves and displays configuration information (addresses and ports) about backend MySQL servers in a routing setup. It performs no writes, deletions, code execution, or financial transactions. The blast radius of misuse is limited to information disclosure of infrastructure details, which is a read-level risk.
From the tool's definition Tool name and description indicate 'List backend MySQL server destinations' — a retrieval operation with no data modification, deletion, or side effects. The verb 'List' and 'Shows' confirm read-only introspection.
Attacks that exploit this kind of access
The rule that runs mysql_router_route_destinations 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_destinations, this is the rule to start with:
mysql_router_route_destinations 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_destinations call is checked against it from then on.
Questions about mysql_router_route_destinations
List backend MySQL server destinations for a route. Shows address and port of each destination server. 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_destinations: 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_destinations 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_destinations 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_destinations. 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_destinations 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