Oracle for Flow Steward

Standalone flowsteward.oracle extension for one Oracle database service. Executes one conservative SELECT (query) or one INSERT, UPDATE, DELETE or MERGE (execute_sql) through a minimal, pinned Google MCP Toolbox v1.3.0 build. No triggers, DDL, PL/SQL, transactions/scripts, wallets, RAC/cluster routing, caller connection strings or executable overrides.

Project connection settings: host, port (1521), service_name, tls (true), allow_writes (false), request_timeout_seconds (15, maximum 30). Secrets: username, password. Public endpoints require verified TLS. Private endpoints require the host administrator's FS_ALLOW_PRIVATE_REMOTE_URLS permission; TLS may be disabled only for private addresses. Use a least-privilege Oracle user. Listener redirects to a different host or port are rejected. DNS is resolved by the host SDK and pinned to the original authority without changing the TLS name.

Inputs: connection_ref, statement, optional positional scalar parameters (array; Oracle binds :1, :2, ...), and max_rows (query only, 1–100). SELECT :1 AS value FROM dual with ["a literal value"] demonstrates binding; values never interpolate into SQL. SQL comments, alternate quoting, DB links, locking and unapproved function calls are rejected. SELECT is intentionally restricted; this is not a general SQL console. Parameters support null, strings, signed 64-bit integers and finite floats; booleans/objects/arrays are rejected. Reads are capped in SQL and iteration at 100 rows and an inline byte budget. Writes require both connection opt-in and a durable host effect claim, are suppressed in test mode, and are never retried automatically. An uncertain post-dispatch write is reported as timeout_unknown, nonretryable.

Linux AMD64 and ARM64 packages each contain exactly one actual pure-Go ELF Toolbox binary. Rebuild with scripts/build_toolbox.sh (Docker required), then package each architecture using python3 scripts/package_extension.py --runtime-target linux-amd64 (or linux-arm64). Pinned source, patches and binary checksums appear in toolbox-provenance.json.

Validation covers standalone contracts, safe SQL/binding, host effect phases, network policy, native ELF/provenance and installer packaging. No Oracle credentials were supplied: a live Oracle connection, server SQL execution and server TLS negotiation have not been verified. Compile and contract evidence must not be read as live integration evidence. The live test reports a skip.

Primary implementation references:

• Google Toolbox Oracle source at the pinned commit

• go-ora v2.9.0 connector

• go-ora TLS network implementation