Overview

Use Oracle Database as a governed source or destination in a Context runbook. Configure the exact records and actions each agent can access.

  • · Vendor-supported OAuth or scoped service credentials
  • · Read and write access configured separately
  • · Tool calls and outcomes recorded per run
Connector contract

Control what agents can do in Oracle Database.

Exact authentication methods and available scopes depend on your Oracle Database plan and deployment. Context keeps the connector configuration explicit.

Read

Read the schemas, tables, and records allowed for the workflow.

Act

Limit inserts or updates to explicitly approved operations.

Verify

Record the query and affected records for review.

Set up the connection

  1. 01

    Authenticate

    Connect Oracle Database with an admin-approved OAuth flow or scoped credential supported by the vendor.

  2. 02

    Choose scope

    Select the accounts, workspaces, projects, or resources available to the runbook.

  3. 03

    Map policy

    Set read and write permissions, reviewer gates, and the identity used for each action.

  4. 04

    Test a run

    Verify one read, one permitted action, and the resulting audit record before rollout.

Build with Oracle Database

Oracle Database can be added to any Context runbook. Start from a prebuilt agent, then choose the resources and actions it needs. Browse all agents →

Connect Oracle Database to Context.

Request demo