Oracle Autonomous Database uses GateRook’s Oracle Database connector. Over TLS without a wallet: allow TLS connections without mutual TLS on the database first.
The screenshots show GateRook 2.0.0: the Oracle Autonomous Database 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 Oracle Autonomous Database, choose its card and select Continue to configure.
Enable TLS connections without mutual TLS for the Autonomous Database and permit your computer through its network access controls.
Get the walletless TLS connection details and a database user and password. The GateRook form does not import a client wallet.
Enter a Name, for example oracle-autonomous-demo. Your AI app uses this name to choose the connection.
Choose Oracle Autonomous Database. Enter a Name, Host, Service name, User and Password from the TLS connection details.
Keep SSL mode at verify-full. The preset Port is 1522; use the port from the database’s TLS connection string, which may be 1521 or 1522.
Enter the full service name, not a TNS alias. Check Default schema and narrow Schema allowlist to the schemas this AI workflow needs.
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 TLS negotiation fails, confirm the database allows walletless TLS rather than requiring mutual TLS. Check its network access list, the selected TLS port and the exact service name.
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 Oracle Autonomous Database on the endpoint and passing its connection test, ask your AI app to use oracle-autonomous-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 the tables visible through my Autonomous Database connection.”
- “Describe the selected Autonomous Database table.”
- “Summarize orders by status in the permitted Autonomous Database 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.