Show comprehensive information about all tables in current database.
AI agents call mysql_show_tables_information to retrieve information from Mcp Windows without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries database metadata to display table information. It retrieves data without modifying, executing arbitrary code, deleting, or committing financial transactions. The scope is limited to metadata inspection of the current database, making it a straightforward Read operation with minimal blast radius if misused.
From the tool's definition Tool name and description indicate a query operation: 'Show comprehensive information about all tables in current database.' The verb 'show' and the informational nature (examining database metadata) confirm this is a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access mysql_show_tables_information gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Windows, and nothing reaches the server without passing your rules. This is the rule we recommend for mysql_show_tables_information:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_show_tables_information": {}
}
}mysql_show_tables_information is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Show comprehensive information about all tables in current database. 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_show_tables_information: 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_show_tables_information 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_show_tables_information 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_show_tables_information. 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_show_tables_information 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.
Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
441 Mcp Windows tools catalogued and risk-classified — across an index of 42,500+ MCP servers.