Google AlloyDB for PostgreSQL
GAManage AlloyDB for PostgreSQL and run SQL, DDL, and vector-similarity search — governed by Cloud IAM.
How it works
Every agent request passes through Ferentin policy before it reaches Google AlloyDB for PostgreSQL.- AI agentAsks for something
- Ferentin policies
- OAuth 2.0 consent
- Cloud iam authorization
- No API keys
- Audit logging
- Google AlloyDB for PostgreSQL MCP serverAuthorized connection
- Governed resultMasked, logged, returned
What you can do with Google AlloyDB for PostgreSQL
Discover
Search and browse what exists, without opening the content itself.
3 tools
Access
Read content and metadata, subject to masking policy.
5 tools
Manage
Create, update, organise and remove items.
9 tools
Technical capabilities17 tools
Discover
- list_clusters
- list_instances
- list_users
Access
- get_cluster
- get_instance
- get_user
- export_data
- get_operation
Manage
- create_cluster
- restore_cluster
- create_backup
- create_instance
- update_instance
- create_user
- execute_sql
- execute_sql_read_only
- import_data
Overview
AlloyDB is Google Cloud's PostgreSQL-compatible database for demanding enterprise workloads, with columnar acceleration and AlloyDB AI (pgvector) for vector-similarity search.
Ferentin integration
Ferentin's Google AlloyDB MCP server connects agents through OAuth2 + Cloud IAM, with tools for cluster/instance/user lifecycle management, SQL and read-only SQL execution, backups, and Cloud Storage import/export. Access is scoped by the signing-in identity's IAM grants.
Frequently asked about Google AlloyDB for PostgreSQL
- What can AI agents do with Google AlloyDB for PostgreSQL through Ferentin?
- Ferentin exposes 17 Google AlloyDB for PostgreSQL MCP tools to your AI agents, grouped as Discover (3 tools), Access (5 tools) and Manage (9 tools). Every call is checked against your Ferentin policies before it reaches Google AlloyDB for PostgreSQL.
- How does Ferentin secure Google AlloyDB for PostgreSQL access?
- Requests through the Google AlloyDB for PostgreSQL integration are covered by OAuth 2.0 consent, cloud iam authorization, no API keys and audit logging. These controls are applied by Ferentin, not by Google AlloyDB for PostgreSQL, so they hold across every connected agent.
- What permissions does the Google AlloyDB for PostgreSQL integration require?
- The Google AlloyDB for PostgreSQL integration requests 1 OAuth 2.0 scope: https://www.googleapis.com/auth/alloydb
- How do I connect Google AlloyDB for PostgreSQL to Ferentin?
- Open the Ferentin admin console, add Google AlloyDB for PostgreSQL as a new connection and authenticate with OAuth 2.0. You then choose which permissions and which tools your agents may use, and the connection goes live for everyone covered by your policies.
- Is the Google AlloyDB for PostgreSQL integration generally available?
- Yes. The Google AlloyDB for PostgreSQL integration is generally available on Ferentin, including the free tier.
Related integrations
3
Google Cloud SQL
Natural-language database operations on Cloud SQL (PostgreSQL/MySQL/SQL Server): run SQL, manage instances, users, and backups.
Google Cloud Spanner
Manage Cloud Spanner instances and databases and run multi-model (SQL + graph GQL) queries — governed by Cloud IAM.
Google BigQuery
Query and explore BigQuery data warehouses. Discover datasets/tables, inspect schema, and run read-only SQL — governed by Cloud IAM.