List tables without primary keys and recommendations.
AI agents call mysql_tables_without_primary_keys 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 performs a read-only operation that queries database metadata to identify tables lacking primary keys and provides recommendations. It has no side effects, does not execute arbitrary code, does not modify data, and does not delete anything. The output is purely informational analysis of existing database structure.
From the tool's definition Tool name 'mysql_tables_without_primary_keys' and description 'List tables without primary keys and recommendations' indicate a query/retrieval operation that returns information about database schema without modifying or deleting data.
Documented attack patterns abuse exactly the kind of access mysql_tables_without_primary_keys 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_tables_without_primary_keys:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_tables_without_primary_keys": {}
}
}mysql_tables_without_primary_keys 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.
List tables without primary keys and recommendations. 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_tables_without_primary_keys: 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_tables_without_primary_keys 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_tables_without_primary_keys 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_tables_without_primary_keys. 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_tables_without_primary_keys 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.