mysql_databases
List all databases accessible to the current user.
This record as markdown: /tools/mukul975-mcp-windows-automation/mysql-databases.md
What mysql_databases does on Mcp Windows
AI agents call mysql_databases to retrieve information from Mcp Windows without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mysql_databases is rated Low
This tool performs a read-only operation to enumerate available databases. It has no side effects, makes no modifications, and presents minimal risk. The severity is low because database enumeration alone does not expose sensitive data and does not enable further exploitation without subsequent tool usage.
From the tool's definition Tool name and description indicate 'List all databases' — a query operation that retrieves information without modifying, deleting, or executing code.
Attacks that exploit this kind of access
The rule that runs mysql_databases safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Windows, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql_databases, this is the rule to start with:
mysql_databases 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 Mcp Windows, apply this rule, and every mysql_databases call is checked against it from then on.
Questions about mysql_databases
List all databases accessible to the current user. It is categorised as a Read tool in the Mcp Windows MCP Server, which means it retrieves data without modifying state.
Register the Mcp Windows MCP server in PolicyLayer and add a rule for mysql_databases: 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 Mcp Windows. Nothing to install.
mysql_databases 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_databases 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_databases. 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_databases is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Windows, and thousands of servers like it.
This server
Across the catalogue