Prisma

Databases, connection strings and object-store buckets. Prisma documents delete_prisma_postgres_database as deleting a database by id, and delete_object_store_bucket as permanently deleting a bucket, every object in it, and all its access keys. Deleting a bucket access key stops that key working immediately. No two-phase confirmation is documented.

Because its only scope is workspace:admin. The server advertises just that plus offline_access at its RFC 9728 metadata endpoint, so there is no read-only grant to choose. Approving the connection gives an agent the same workspace authority you hold, including database and bucket deletion. Review it on that basis.

Yes. execute_sql_query runs a SQL query against a database by id, and execute_prisma_postgres_schema_update applies a schema change. Prisma also exposes introspect_database_schema for reading structure first. These are ordinary tool calls, so whatever approval prompt your client shows is the only gate in front of them.

No. Every data tool names Prisma Postgres specifically, and Prisma describes the server as letting AI tools manage Prisma Postgres databases. The one exception is search_prisma_documentation, which answers questions about Prisma ORM, Postgres, Compute, schema design and migrations from the official docs.

Only from a backup you already had. Prisma exposes list_prisma_postgres_backups and create_prisma_postgres_recovery, which restores a backup to a new database. Recovery creates a new database rather than restoring in place, and nothing in the documented tool set recovers a bucket, whose deletion Prisma calls permanent.

Yes. Prisma states search_prisma_documentation is read-only and needs no setup beyond the MCP connection. It returns a cited answer with links back to the official documentation, so answers reflect the current docs rather than a model's training data. It is the only tool on the server that touches no workspace resource.