mysql_router_route_status
Get operational status of a specific route including active connections, total connections, and blocked hosts count.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-router-route-status.md
What mysql_router_route_status does on Mysql Mcp
AI agents call mysql_router_route_status 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_status is rated Low
This tool retrieves monitoring/diagnostic information about MySQL Router routes and their connection metrics. It performs no writes, deletions, executions, or financial operations. The worst-case misuse would be information disclosure (e.g., discovering internal connection patterns), which poses minimal blast radius for a monitoring endpoint. Classified as Read with low severity.
From the tool's definition Tool name and description indicate 'Get operational status' of a route, reporting 'active connections, total connections, and blocked hosts count'—purely informational queries with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
The rule that runs mysql_router_route_status 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_status, this is the rule to start with:
mysql_router_route_status 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_status call is checked against it from then on.
Questions about mysql_router_route_status
Get operational status of a specific route including active connections, total connections, and blocked hosts count. 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_status: 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_status 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_status 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_status. 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_status 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