---
title: "Discussion on \"You Don’t Need to Know Anything Anymore\" | Hashnode"
description: "Discussion on \"You Don’t Need to Know Anything Anymore\". Codex and OCI CLI built an MCP server for an Oracle APEX app. The experience showed why knowing what good looks like still matters."
url: "https://hashnode.com/posts/you-don-t-need-to-know-anything-anymore/6ae33ded0435fdb24bf98f98"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [You Don’t Need to Know Anything Anymore](https://blog.cloudnueva.com/you-don-t-need-to-know-anything-anymore?utm_source=hashnode&utm_medium=feed)

Codex and OCI CLI built an MCP server for an Oracle APEX app. The experience showed why knowing what good looks like still matters.

Oct 29 · 2 min read · blog.cloudnueva.com  
Read the article

-   [#orclapex](https://hashnode.com/tag/orclapex)
-   [#aiagents](https://hashnode.com/tag/aiagents)

## Written by

[Jon Dixon](https://hashnode.com/@orclapex)

@orclapex · San Diego, CA

  
[View profile](https://hashnode.com/@orclapex)

APEX, ORDS & the Oracle Database

I’m Jon Dixon, an Oracle APEX developer and consultant at Cloud Nueva. I write about APEX, ORDS, the Oracle Database, and how AI is changing the way we build software. This blog is where I share practical examples, lessons learned, and ideas from my work.

## Responses 5

Markdown supported · ⌘↵ to post

[Julian Neagu](https://hashnode.com/@julianneagulab)

[Nov 2](https://hashnode.com/posts/you-don-t-need-to-know-anything-anymore/6ae33ded0435fdb24bf98f98/comment/6ae82e42b5794731815c9184)

I've been building small tools with AI, and this really hits home. I don't need to know every detail of a new stack, but I do need to know enough to spot bad decisions before they become bigger problems.

[Jon Dixon](https://hashnode.com/@orclapex)

[Nov 2](https://hashnode.com/posts/you-don-t-need-to-know-anything-anymore/6ae33ded0435fdb24bf98f98/comment/6ae82e42b5794731815c9184#reply-6ae8abb8cbf3801f14214f0f)

Exactly, Julian. With Genie, I could spend less time learning the OCI setup steps because I already understood the application and the security boundaries I needed. That gave me something concrete to check the result against. Without that understanding, it would be much harder to spot a bad decision.

[WIO](https://hashnode.com/@xwiox)

[Oct 30](https://hashnode.com/posts/you-don-t-need-to-know-anything-anymore/6ae33ded0435fdb24bf98f98/comment/6ae3e738a6c2dfa34887a570)

the "knowing what good looks like" bit is what I keep wondering about. when the agent is running OCI CLI commands for you, how do you actually review that it didn't leave something too permissive, like those 2 IAM policies? do you read the diff or just test the outcome?

[Jon Dixon](https://hashnode.com/@orclapex)

[Oct 30](https://hashnode.com/posts/you-don-t-need-to-know-anything-anymore/6ae33ded0435fdb24bf98f98/comment/6ae3e738a6c2dfa34887a570#reply-6ae3ec51499df2d19b1cab91)

Good point. I do understand IAM policies and sense checked them myself to make sure they only covered the MCP group that was created and don't provide access to any other OCI services.

Also, in this case, IAM is really only being used for Authentication. Authorization is being handled in the database. I tie the IAM user to a local user access table in the DB, and the DB logic and a VPD determine what the user has access to.

[WIO](https://hashnode.com/@xwiox)

[Oct 30](https://hashnode.com/posts/you-don-t-need-to-know-anything-anymore/6ae33ded0435fdb24bf98f98/comment/6ae3e738a6c2dfa34887a570#reply-6ae414d1dbf0dcc99a558731)

got it, keeping IAM for auth and pushing authorization into the DB is a cleaner split than i was picturing. thanks for walking through it.
