# mysql_read_query

Execute a read-only SQL query (SELECT). Uses prepared statements for safety.

Agent View of the PolicyLayer registry record for `mysql_read_query`. HTML page: https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-read-query

## Facts

- Tool: `mysql_read_query`
- Server: Mysql Mcp (`oci:docker.io/writenotenow/mysql-mcp:v1.0.0`) — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp.md
- Homepage: https://github.com/neverinfamous/mysql-mcp.git
- 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_read_query",
    "arguments": {}
  }
}
```

## Why mysql_read_query is rated Low

This tool only retrieves or queries data via SELECT statements with no side effects. While SQL injection is theoretically possible, the description confirms use of prepared statements which mitigate that risk. The read-only constraint means no data modification, deletion, or execution of arbitrary code is possible.

From the tool's own definition: "Tool name is 'mysql_read_query' and description explicitly states 'Execute a read-only SQL query (SELECT)' with prepared statements for safety."

## Use case

AI agents call mysql_read_query 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mysql Mcp:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "mysql_read_query": {}
  }
}
```

## Other tools on Mysql Mcp (222)

- `mysql_audit_restore_backup` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-audit-restore-backup.md
- `mysql_cascade_simulator` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-cascade-simulator.md
- `mysql_doc_drop_collection` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-doc-drop-collection.md
- `mysql_doc_remove` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-doc-remove.md
- `mysql_drop_partition` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-drop-partition.md
- `mysql_drop_schema` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-drop-schema.md
- `mysql_drop_table` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-drop-table.md
- `mysql_drop_view` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-drop-view.md
- `mysql_event_drop` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-event-drop.md
- `mysql_force_index` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-force-index.md
- `mysql_fulltext_drop` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-fulltext-drop.md
- `mysql_json_remove` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-json-remove.md
- `mysql_migration_rollback` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-migration-rollback.md
- `mysql_role_drop` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-role-drop.md
- `mysql_analyze_table` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-analyze-table.md
- `mysql_create_dump` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-create-dump.md
- `mysql_event_create` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-event-create.md
- `mysql_flush_tables` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-flush-tables.md
- `mysql_json_merge` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-json-merge.md
- `mysql_migration_apply` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-migration-apply.md
- `mysql_optimize_table` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-optimize-table.md
- `mysql_spatial_intersection` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-spatial-intersection.md
- `mysql_spatial_transform` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-spatial-transform.md
- `mysql_stats_row_number` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-stats-row-number.md
- `mysql_transaction_begin` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-transaction-begin.md
- `mysql_transaction_execute` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-transaction-execute.md
- `mysqlsh_run_script` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysqlsh-run-script.md
- `proxysql_commands` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/proxysql-commands.md
- `mysql_audit_diff_backup` — Read — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-audit-diff-backup.md
- `mysql_audit_list_backups` — Read — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-audit-list-backups.md
- …and 192 more: https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp.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=io-github-neverinfamous-mysql-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-neverinfamous-mysql-mcp