Google Cloud SQL MCP server
15 tools · Last check that passed 27 Oct 2026, 01:50 UTC
Google's own remote MCP server for Cloud SQL gives an agent the instances, database users and backups of the Google Cloud projects its sign-in reaches, and runs SQL on their databases. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 15 tools
| Tool | Counted as |
|---|---|
execute_sql | Deletes |
restore_backup | Deletes |
update_instance | Deletes |
clone_instance | Changes things |
create_backup | Changes things |
create_instance | Changes things |
create_user | Changes things |
execute_sql_readonly | Changes things |
import_data | Changes things |
postgres_upgrade_precheck | Changes things |
update_user | Changes things |
get_instance | Said to only read |
get_operation | Said to only read |
list_instances | Said to only read |
list_users | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
12 of the last 12 checks passed
A check passes when the server lists its tools. Checked at https://sqladmin.googleapis.com/mcp.
Recent changes
24 Oct 2026, 13:23 UTC, after a check on 24 Oct 2026, 06:14 UTC
Inputs or outputs changed on clone_instance, create_backup, create_instance, create_user, get_operation and 5 more.
24 Oct 2026, 06:14 UTC, after a check on 23 Oct 2026, 09:57 UTC
Inputs or outputs changed on clone_instance, create_backup, create_instance, create_user, get_operation and 5 more.
21 Oct 2026, 09:36 UTC, after a check on 20 Oct 2026, 09:45 UTC
Inputs or outputs changed on clone_instance, create_backup, create_instance, create_user, get_operation and 5 more.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when Google Cloud SQL's tools change.
One email when Google Cloud SQL's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- Its execute_sql tool runs any valid SQL statement, including statements that change schemas, permissions and data. Google's Cloud SQL MCP documentation
- Other tools create, clone, update and restore instances, create and update database users, and import data from Cloud Storage. Google's Cloud SQL MCP documentation
- Rows read from the databases come back to the agent, and text an agent reads can carry instructions for it. OWASP, prompt injection
How to limit it
With Google Cloud SQL's own settings, as its documentation describes them. Stackduke has not tested them.
- Connect to the address ending in /mcp/readonly when the agent only needs to read. Google lists only read-only tools there, including read-only SQL. Google's Cloud SQL MCP documentation
- Sign in with the cloudsql.readonly scope, which Google lists for viewing resources and running read-only SQL. Google's Cloud SQL MCP documentation
- IAM allow and deny policies can allow or refuse tool calls by principal, by service or tool name, by the application's OAuth client, or by whether a tool is marked read-only. Google's Cloud SQL MCP documentation
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.