# Prisma Your Toolhouse AI Worker can connect to Prisma using 22 specialized tools. ## Auth Connection This service requires an auth connection to use its tools. You can set this up in your Toolhouse dashboard under [Auth Connections](https://toolhouse.app/auth-connections?authkit_slugs=prisma). ## Tools (22) ### `Prisma Create Connection` Integration name: **PRISMA\_CREATE\_CONNECTION** Create new API key connection for database access. Creates connection string with embedded credentials for application database access. Returns complete connection details ready for immediate use. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------ | ------ | :------: | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | string | ✅ | — | Human-readable name for the new connection/API key. This will be displayed in UIs and used for identification. Choose descriptive names like 'Production API Key', 'Analytics Access', 'Dev Environment', etc. | | `databaseId` | string | ✅ | — | Unique database identifier to create connection for (format: 'db\_xxxxx'). Must be a database the authenticated user has write access to. The new connection will provide API key access to this database. | *** ### `Prisma Create Database` Integration name: **PRISMA\_CREATE\_DATABASE** Create new postgres database in an existing Prisma project. Creates database in specified region with connection strings and API keys. Returns complete database details ready for immediate use. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------- | ------- | :------: | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | string | ✅ | — | Human-readable name for the new database. This will be displayed in UIs and used for identification. Choose descriptive names like 'Production DB', 'Analytics', etc. | | `region` | string | ✅ | — | AWS region where the database will be deployed. Valid values: 'us-east-1', 'us-west-1', 'eu-central-1', 'eu-west-3', 'ap-southeast-1', 'ap-northeast-1'. Choose region closest to your users for optimal performance. Use LIST\_POSTGRES\_REGIONS to get current available regions. | | `isDefault` | boolean | | — | Whether this database should be the default for the project. Default false. Only one database can be default per project. Setting to true will make other databases non-default. | | `projectId` | string | ✅ | — | Unique project identifier to create database in (format: 'prj\_xxxxx'). Must be a project the authenticated user has write access to. The new database will belong to this project. | *** ### `Prisma Create Project` Integration name: **PRISMA\_CREATE\_PROJECT** Create new Prisma project with managed postgres database. Creates project in authenticated user's workspace with postgres database in specified region. Returns complete project details including connection strings and API keys. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | string | ✅ | — | Human-readable name for the new project. This will be displayed in UIs and used for identification. Choose descriptive names like 'Production API', 'Dev Environment', etc. | | `region` | string | ✅ | — | AWS region where the postgres database will be deployed. Available regions: 'us-east-1', 'us-west-1', 'eu-central-1', 'eu-west-3', 'ap-southeast-1', 'ap-northeast-1'. Choose region closest to your users for optimal performance. | *** ### `Prisma Delete Connection` Integration name: **PRISMA\_DELETE\_CONNECTION** Permanently delete database connection and revoke API key access. WARNING: This immediately revokes database access for any applications using this connection string. Ensure no critical systems depend on this connection. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | string | ✅ | — | Unique connection identifier to delete (format: 'con\_xxxxx'). WARNING: This permanently revokes API key access to the database. Any applications using this connection string will lose access immediately. This action cannot be undone - ensure no critical systems depend on this connection. | *** ### `Prisma Delete Database` Integration name: **PRISMA\_DELETE\_DATABASE** Permanently delete Prisma database and all stored data. WARNING: This action cannot be undone. All data in the database will be permanently destroyed. Default databases typically cannot be deleted. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------ | ------ | :------: | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `databaseId` | string | ✅ | — | Unique database identifier to delete (format: 'db\_xxxxx'). WARNING: This permanently deletes the database and all stored data. Default databases typically cannot be deleted. This action cannot be undone. Ensure all important data is backed up before deletion. | *** ### `Prisma Delete Project` Integration name: **PRISMA\_DELETE\_PROJECT** Permanently delete Prisma project and all associated resources. WARNING: This action cannot be undone. All databases, environments, and project data will be permanently destroyed. Use with extreme caution in production environments. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | string | ✅ | — | Unique project identifier to delete (format: 'proj\_xxxxx'). WARNING: This permanently deletes the project and all associated data including databases, environments, and configurations. This action cannot be undone. Ensure all important data is backed up before deletion. | *** ### `Prisma Execute Sql Command` Integration name: **PRISMA\_EXECUTE\_SQL\_COMMAND** Execute SQL commands that modify database data or structure. Runs INSERT, UPDATE, DELETE, CREATE TABLE, and other data modification commands safely through PostgreSQL driver with parameterized query support. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------ | ------ | :------: | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `command` | string | ✅ | — | SQL command to execute against the database (INSERT, UPDATE, DELETE, CREATE TABLE, etc.). Examples: 'INSERT INTO users (name, email) VALUES ($1, $2)', 'UPDATE users SET active = $1 WHERE id = $2', 'DELETE FROM sessions WHERE expires\_at < NOW()', 'CREATE TABLE logs (id SERIAL PRIMARY KEY, message TEXT, created\_at TIMESTAMP DEFAULT NOW())' | | `parameters` | array | | — | Optional array of parameters for parameterized commands using $1, $2, etc. placeholders. Example: command='INSERT INTO users (name, email) VALUES ($1, $2)', parameters=\['John Doe', '']. Parameters are automatically escaped to prevent SQL injection. | | `connectionString` | string | ✅ | — | PostgreSQL connection string for direct database access. Use the standard format: 'postgresql://USER:PASSWORD\@HOST:PORT/DATABASE?sslmode=require'. Get credentials from create\_connection or create\_database response fields: use 'user' as USER, 'pass' as PASSWORD, and 'host' as HOST:PORT. Example: 'postgresql://user::5432/postgres?sslmode=require'. Note: Do NOT use Prisma Accelerate URLs (prisma+postgres\://accelerate.prisma-data.net/...) - those are for Prisma Client SDK only. Use the direct connection credentials instead. | *** ### `Prisma Execute Sql Query` Integration name: **PRISMA\_EXECUTE\_SQL\_QUERY** Execute SQL SELECT queries against Prisma Postgres databases. Runs read-only queries safely through direct PostgreSQL connection with SSL. Uses credentials from create\_connection action (host, user, pass fields). Perfect for data analysis, schema inspection, and reporting operations. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------ | ------ | :------: | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `host` | string | ✅ | — | Database host with port (format: 'db.prisma.io:5432'). Obtain this from create\_connection action response field 'host'. This is the direct PostgreSQL endpoint for your Prisma Postgres database. | | `user` | string | ✅ | — | Database username (tenant ID from Prisma). Obtain this from create\_connection action response field 'user'. This is a unique identifier for your database tenant. | | `query` | string | ✅ | — | SQL SELECT query to execute against the database. Use standard PostgreSQL syntax. Common examples: 'SELECT \* FROM users LIMIT 10', 'SELECT name, email FROM customers WHERE active = true', 'SELECT table\_name FROM information\_schema.tables WHERE table\_schema = 'public''. Avoid INSERT/UPDATE/DELETE - use execute\_sql\_command for those operations. | | `password` | string | ✅ | — | Database password (secret key from Prisma). Obtain this from create\_connection action response field 'pass'. Format is typically 'sk\_xxxxx'. Keep this secure. | | `parameters` | array | | — | Optional array of parameters for parameterized queries using %s placeholders. Example: query='SELECT \* FROM users WHERE id = %s AND active = %s', parameters=\[123, true]. Parameters are automatically escaped to prevent SQL injection. Use %s for each parameter in order they appear in the query. | *** ### `Prisma Get Database` Integration name: **PRISMA\_GET\_DATABASE** Retrieve specific Prisma database by ID. Returns database details including status, project context, and regional deployment. Use for database monitoring, validation, and administrative operations. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------ | ------ | :------: | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `databaseId` | string | ✅ | — | Unique database identifier to retrieve (format: 'db\_xxxxx'). This ID is obtained from database listing or creation operations. Must be a database the authenticated user has access to. | *** ### `Prisma Get Database Usage` Integration name: **PRISMA\_GET\_DATABASE\_USAGE** Retrieve usage metrics for a specific Prisma database. Returns metrics including storage usage and operation counts (reads/writes) for the specified time period. Use for monitoring resource consumption, cost analysis, and capacity planning. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------ | ------ | :------: | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `endDate` | string | | — | End date for metrics query in ISO 8601 format (e.g., '2025-07-31T23:59:59Z'). Defaults to current date if not provided. Will be set to end of day if a future date is provided. | | `startDate` | string | | — | Start date for metrics query in ISO 8601 format (e.g., '2025-07-01T00:00:00Z'). Defaults to start of current month if not provided. Use to specify custom date ranges for usage analysis. | | `databaseId` | string | ✅ | — | Unique database identifier to retrieve usage metrics for (format: 'db\_xxxxx'). Must be a database the authenticated user has access to. This ID is obtained from database listing or creation operations. | *** ### `Prisma Get Project` Integration name: **PRISMA\_GET\_PROJECT** Retrieve specific Prisma project by ID. Returns project details including name, creation timestamp, and workspace information. Use for project detail views, validation, and administrative operations. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | string | ✅ | — | Unique project identifier to retrieve (format: 'proj\_xxxxx'). This ID is obtained from project listing or creation operations. Must be a project the authenticated user has access to. | *** ### `Prisma Inspect Database Schema` Integration name: **PRISMA\_INSPECT\_DATABASE\_SCHEMA** Inspect database schema structure and table information. Returns comprehensive schema details including tables, columns, data types, constraints, and relationships. Essential for understanding database structure before executing queries. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------- | ------- | :------: | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `host` | string | ✅ | — | Database host with port (format: 'db.prisma.io:5432'). Obtain this from create\_connection action response field 'host'. This is the direct PostgreSQL endpoint for your Prisma Postgres database. | | `user` | string | ✅ | — | Database username (tenant ID from Prisma). Obtain this from create\_connection action response field 'user'. This is a unique identifier for your database tenant. | | `password` | string | ✅ | — | Database password (secret key from Prisma). Obtain this from create\_connection action response field 'pass'. Format is typically 'sk\_xxxxx'. Keep this secure. | | `tableName` | string | | — | Optional specific table name to inspect. If provided, returns detailed column information for that table only. If omitted, returns overview of all tables in the database. Use for focused schema analysis of specific tables. | | `includeIndexes` | boolean | | — | Whether to include index information in the schema results. When true, shows primary keys, foreign keys, and other indexes. Useful for understanding table relationships and query optimization. | *** ### `Prisma List Accelerate Regions` Integration name: **PRISMA\_LIST\_ACCELERATE\_REGIONS** Retrieve all available regions for Prisma Accelerate. Returns regions where Accelerate global database cache can be deployed. Use for cache region selection to minimize latency for your users. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. *No parameters required.* *** ### `Prisma List Backups` Integration name: **PRISMA\_LIST\_BACKUPS** Retrieve list of available backups for a specific database. Returns backup details including status, size, type, and restoration readiness. Use for backup monitoring, restoration planning, and compliance auditing. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------ | ------- | :------: | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `limit` | integer | | — | Maximum number of backups to return in a single request. Defaults to 25 if not specified. Typical range is 1-100. Use smaller values (10-25) for UI pagination, larger values (50-100) for processing. | | `databaseId` | string | ✅ | — | Unique database identifier to list backups for (format: 'db\_xxxxx'). Must be a database the authenticated user has access to. All available backups for this database will be returned. | *** ### `Prisma List Connections` Integration name: **PRISMA\_LIST\_CONNECTIONS** Retrieve paginated list of connections for a specific database. Returns connection details including names, creation dates, and database context. Use for API key management, security audits, and access control. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------ | ------- | :------: | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `limit` | integer | | — | Maximum number of connections to return in a single request. Defaults to 100 if not specified. Valid range is typically 1-500. Use smaller values (10-50) for faster responses when you only need a few connections, or larger values (100-500) when bulk processing. | | `cursor` | string | | — | Pagination cursor for retrieving the next page of results. Use the 'nextCursor' value from a previous response to get subsequent pages. Leave as None/null for the first page. Enables efficient pagination through large numbers of connections without missing or duplicating entries. | | `databaseId` | string | ✅ | — | Unique database identifier to list connections for (format: 'db\_xxxxx'). Must be a database the authenticated user has access to. All connection strings and API keys for this database will be returned. | *** ### `Prisma List Databases` Integration name: **PRISMA\_LIST\_DATABASES** Retrieve paginated list of databases for a specific Prisma project. Returns database details including status, region, and project context. Use for database discovery, monitoring, and project administration. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ----------- | ------- | :------: | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `limit` | integer | | — | Maximum number of databases to return in a single request. Defaults to 100 if not specified. Valid range is typically 1-500. Use smaller values (10-50) for faster responses when you only need a few databases, or larger values (100-500) when bulk processing. | | `cursor` | string | | — | Pagination cursor for retrieving the next page of results. Use the 'nextCursor' value from a previous response to get subsequent pages. Leave as None/null for the first page. Enables efficient pagination through large numbers of databases without missing or duplicating entries. | | `projectId` | string | ✅ | — | Unique project identifier to list databases for (format: 'prj\_xxxxx'). Must be a project the authenticated user has access to. All databases belonging to this project will be returned. | *** ### `Prisma List Postgres Regions` Integration name: **PRISMA\_LIST\_POSTGRES\_REGIONS** Retrieve all available regions for Prisma Postgres. Returns regions where Prisma Postgres databases can be deployed with current availability status. Use for region selection during database creation and capacity planning. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. *No parameters required.* *** ### `Prisma List Projects` Integration name: **PRISMA\_LIST\_PROJECTS** Retrieve paginated list of Prisma projects accessible to authenticated user. Returns project IDs, names, workspace info, and timestamps with cursor-based pagination. Use for project discovery, UI selection flows, and administrative operations. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------- | :------: | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `limit` | integer | | — | Maximum number of projects to return in a single request. Defaults to 100 if not specified. Valid range is typically 1-500. Use smaller values (10-50) for faster responses when you only need a few projects, or larger values (100-500) when bulk processing. The API may return fewer results than requested if fewer projects exist. | | `cursor` | string | | — | Pagination cursor for retrieving the next page of results. Use the 'nextCursor' value from a previous response to get subsequent pages. Leave as None/null for the first page. This enables efficient pagination through large numbers of projects without missing or duplicating entries. | *** ### `Prisma List Workspace Integrations` Integration name: **PRISMA\_LIST\_WORKSPACE\_INTEGRATIONS** Retrieve paginated list of integrations for a specific Prisma workspace. Returns integration details including OAuth client info, granted scopes, and creator. Use for security audits, integration management, and workspace administration. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------- | :------: | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `limit` | integer | | — | Maximum number of integrations to return in a single request. Defaults to 100 if not specified. Valid range is typically 1-500. Use smaller values (10-50) for faster responses when you only need a few integrations, or larger values (100-500) when bulk processing. | | `cursor` | string | | — | Pagination cursor for retrieving the next page of results. Use the 'nextCursor' value from a previous response to get subsequent pages. Leave as None/null for the first page. Enables efficient pagination through large numbers of integrations without missing or duplicating entries. | | `workspaceId` | string | ✅ | — | Unique workspace identifier to list integrations for (format: 'wksp\_xxxxx'). Must be a workspace the authenticated user has access to. All integrations belonging to this workspace will be returned. | *** ### `Prisma List Workspaces` Integration name: **PRISMA\_LIST\_WORKSPACES** Retrieve paginated list of Prisma workspaces accessible to authenticated user. Returns workspace IDs, names, creation timestamps with cursor-based pagination. Use for workspace discovery, UI selection flows, and administrative operations. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------- | :------: | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `limit` | integer | | — | Maximum number of workspaces to return in a single request. Defaults to 100 if not specified. Valid range is typically 1-500. Use smaller values (10-50) for faster responses when you only need a few workspaces, or larger values (100-500) when bulk processing. The API may return fewer results than requested if fewer workspaces exist. | | `cursor` | string | | — | Pagination cursor for retrieving the next page of results. Use the 'nextCursor' value from a previous response to get subsequent pages. Leave as None/null for the first page. This enables efficient pagination through large numbers of workspaces without missing or duplicating entries. | *** ### `Prisma Restore Backup` Integration name: **PRISMA\_RESTORE\_BACKUP** Restore database backup to new database instance. Creates new database from existing backup with specified name. Operation is asynchronous - monitor the returned database status for completion. Restoration may take several minutes. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | -------------------- | ------ | :------: | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `backupId` | string | ✅ | — | Unique backup identifier to restore. Must be a completed backup from the specified database. Use list\_backups action to find available backup IDs. | | `databaseId` | string | ✅ | — | Unique source database identifier containing the backup (format: 'db\_xxxxx'). Must be a database the authenticated user has access to. The backup will be restored from this database's backup collection. | | `targetDatabaseName` | string | ✅ | — | Name for the new database created from backup restoration. This will be displayed in UIs and used for identification. Choose descriptive names like 'Restored DB 2025-01-20', 'Production Rollback', etc. | *** ### `Prisma Transfer Project` Integration name: **PRISMA\_TRANSFER\_PROJECT** Transfer Prisma project ownership to another user's workspace. Transfers project ownership from the current authenticated user to the recipient specified by their OAuth2 access token. This is typically used in partner integrations where databases are provisioned on the partner's workspace and later transferred to end users. The project and all its databases are moved to the recipient's workspace. The current owner loses access unless the new owner explicitly grants it. Requirements: - Valid project ID owned by the current user - Valid OAuth2 access token for the recipient user - Recipient workspace must have sufficient quota for the project #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------------- | ------ | :------: | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | string | ✅ | — | Unique project identifier to transfer (format: 'proj\_xxxxx'). Obtain from PRISMA\_LIST\_PROJECTS or PRISMA\_CREATE\_PROJECT response. Must be a project owned by the authenticated user's workspace. After transfer, the current user loses access unless explicitly granted by the new owner. | | `recipientAccessToken` | string | ✅ | — | OAuth2 access token of the recipient user who will receive project ownership. This token must be obtained through Prisma's OAuth2 flow for the recipient user. The recipient workspace must have sufficient quota to receive the project. Typically used in partner integrations to transfer provisioned databases to end users. | *** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.toolhouse.ai/toolhouse/integrations/prisma.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.