Oracle Integration MCP Gateway in 26.10: how are you governing AI agent access to OIC integrations?

OIC 26.10 shipped the MCP Gateway in September, and I have been reading through how it is meant to work. Instead of pointing every AI agent straight at every MCP server (OIC-hosted or third-party), agents connect to one gateway endpoint. The gateway handles identity, tool filtering, policies (Oracle’s demo shows tool filter, PII and business rule policies), credential resolution and audit.

What I like on paper: agents do not hold downstream credentials, and you can expose only approved tools instead of a whole server. What I am still unsure about, because it is a first iteration:

1. How do policies behave when gateway-level, server-level and tool-level rules overlap?
2. Which authentication methods are supported for the MCP clients calling the gateway?
3. Where does the audit data end up, and for how long?
4. Has anyone converted an existing integration into an MCP tool yet? What broke first?

If you have tried it in a test tenant, share what you found. If you have not, tell me which integration you would expose to an agent first, and which one you would never expose without a human approval step.

Full breakdown of the setup flow and common mistakes: https://lanverse.in/blog/oracle-integration-mcp-gateway-26-10