Amazon RDS for Oracle uses GateRook’s Oracle Database connector. With a database user and password. For full verification, paste the Amazon RDS CA bundle.
The screenshots show GateRook 2.0.0: the Amazon RDS for Oracle form, the endpoint selector, and this connector’s actual tool preview. The form and preview have not been saved. Select a screenshot to open it at full size.
1. Create a connection and enter the settings
In GateRook, open Connections, select Add connection, search for Amazon RDS for Oracle, choose its card and select Continue to configure.
Obtain the RDS for Oracle hostname, its configured TLS listener port and an Oracle database user and password.
Ask your database administrator for the registered Oracle service name. GateRook’s Service name field does not accept a SID or a TNS alias.
Enter a Name, for example aws-rds-oracle-demo. Your AI app uses this name to choose the connection.
Choose Amazon RDS for Oracle. Enter a Name, endpoint Host, the TLS Port, Service name, User and Password.
Set SSL mode to verify-full and paste the Amazon RDS CA bundle into CA certificate (PEM). RDS Oracle uses a separate port for TLS; use the one configured in its SSL option.
Set Default schema only if it differs from the user’s own schema. Use Schema allowlist to select the schemas your AI may access; unquoted Oracle schema names use uppercase.
Choose Development, Staging or Production to match the service. Review the connector’s limit and access settings before continuing.
2. Test the connection and add it to an endpoint
Select Continue to test. GateRook checks the settings from your computer. Review the result and resolve any connection, certificate or permission error before continuing.
If the listener rejects the connection, verify the registered service name and the TLS port with the database administrator. An RDS example that uses a SID cannot be pasted into this service-name field.
After the test passes, select Continue to add to an endpoint. Choose the endpoint your AI app uses, review its tool modes, then select Save connection. GateRook offers default as the starter endpoint.
3. Use the connection from your AI IDE
After saving Amazon RDS for Oracle on the endpoint and passing its connection test, ask your AI app to use aws-rds-oracle-demo, or the name you chose. If its tools are missing, confirm the endpoint assignment and refresh the MCP connection or start a new chat.
The preview below shows this connector’s default tools before saving. The table explains what each tool can do; connection settings, credentials and endpoint policies can restrict access further.
Start with a small read request. Replace example resource names with existing resources your connection may access. Open Activity after the call to inspect its connection, tool, arguments, policy decision and result metadata.
Ask your AI, for example
- “List schemas and tables visible to my RDS Oracle account.”
- “Describe the columns and keys of the selected Oracle table.”
- “Count orders by status in the permitted Oracle schema.”
| Tool | What it does | Starts as |
|---|---|---|
sql_list_schemas | List accessible Oracle schemas, tables and views within the connection and policy restrictions. | Read only |
sql_describe_table | Describe an Oracle table’s columns, types, keys and indexes where available. | Read only |
sql_query | Run one validated Oracle read statement in a read-only transaction, then roll it back. Only supported built-in SQL functions are admitted; database privileges still govern views and stored expressions. | Read only |
sql_execute | Run one supported data or schema change with Approval by default. Database permissions and the environment policy apply; Oracle schema changes can commit implicitly. | Approval |
You can change each tool’s mode on the endpoint. Every call your AI makes appears in Activity.