# mysql_show_table_constraints Show constraints for a given table (primary keys, unique, foreign keys). Agent View of the PolicyLayer registry record for `mysql_show_table_constraints`. HTML page: https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-show-table-constraints ## Facts - Tool: `mysql_show_table_constraints` - Server: Mysql (`mukul975/mysql-mcp-server`) — https://policylayer.com/tools/mukul975-mysql-mcp-server.md - Homepage: https://github.com/mukul975/mysql-mcp-server - Risk category: Read (Low risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Allowed ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "mysql_show_table_constraints", "arguments": {} } } ``` ## Why mysql_show_table_constraints is rated Low This tool retrieves metadata about table constraints (primary keys, unique constraints, foreign keys) without modifying data or schema. It is a query operation with no side effects, fitting the 'Read' category. Severity is low because constraint metadata disclosure has minimal impact on confidentiality or system integrity compared to data exfiltration or destructive operations. From the tool's own definition: "Tool name is 'mysql_show_table_constraints' and description states it shows (retrieves) constraints for a table with no modification capability. No write, delete, or execution of arbitrary operations is mentioned." ## Use case AI agents call mysql_show_table_constraints to retrieve information from Mysql without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere. ## Recommended policy (PolicyLayer) Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mysql: ```json { "version": "1", "default": "deny", "tools": { "mysql_show_table_constraints": {} } } ``` ## Other tools on Mysql (232) - `drop_event` — Destructive — https://policylayer.com/tools/mukul975-mysql-mcp-server/drop-event.md - `drop_partition` — Destructive — https://policylayer.com/tools/mukul975-mysql-mcp-server/drop-partition.md - `drop_role` — Destructive — https://policylayer.com/tools/mukul975-mysql-mcp-server/drop-role.md - `drop_stored_function` — Destructive — https://policylayer.com/tools/mukul975-mysql-mcp-server/drop-stored-function.md - `drop_stored_procedure` — Destructive — https://policylayer.com/tools/mukul975-mysql-mcp-server/drop-stored-procedure.md - `mysql_alter_table_drop_column` — Destructive — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-alter-table-drop-column.md - `mysql_delete_data` — Destructive — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-delete-data.md - `mysql_drop_database` — Destructive — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-drop-database.md - `mysql_drop_foreign_key` — Destructive — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-drop-foreign-key.md - `mysql_drop_index` — Destructive — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-drop-index.md - `mysql_drop_primary_key` — Destructive — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-drop-primary-key.md - `mysql_drop_table` — Destructive — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-drop-table.md - `mysql_drop_user` — Destructive — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-drop-user.md - `mysql_drop_view` — Destructive — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-drop-view.md - `mysql_kill_process` — Destructive — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-kill-process.md - `mysql_reset_query_cache` — Destructive — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-reset-query-cache.md - `mysql_revoke_privileges` — Destructive — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-revoke-privileges.md - `mysql_truncate_table` — Destructive — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-truncate-table.md - `create_event` — Execute — https://policylayer.com/tools/mukul975-mysql-mcp-server/create-event.md - `create_stored_procedure` — Execute — https://policylayer.com/tools/mukul975-mysql-mcp-server/create-stored-procedure.md - `mysql_analyze_table` — Execute — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-analyze-table.md - `mysql_auto_index_rebuild_scheduler` — Execute — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-auto-index-rebuild-scheduler.md - `mysql_flush_logs` — Execute — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-flush-logs.md - `mysql_flush_privileges` — Execute — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-flush-privileges.md - `mysql_flush_tables` — Execute — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-flush-tables.md - `mysql_lock_tables` — Execute — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-lock-tables.md - `mysql_optimize_table` — Execute — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-optimize-table.md - `mysql_repair_table` — Execute — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-repair-table.md - `mysql_set_variable` — Execute — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-set-variable.md - `mysql_unlock_tables` — Execute — https://policylayer.com/tools/mukul975-mysql-mcp-server/mysql-unlock-tables.md - …and 202 more: https://policylayer.com/tools/mukul975-mysql-mcp-server.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=mukul975-mysql-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/mukul975-mysql-mcp-server