The Problem Is Irreversibility
When an AI agent can clone a repository, mine a knowledge base, draft a post, and publish it to the open web without a human in the loop, the failure mode is not a typo. It is a leaked credential that is indexed by Google within minutes and scraped by bots within seconds. A leaked key is unrecoverable once public. Rotation helps, but the window between exposure and rotation is enough to drain a cloud account, exfiltrate a database, or compromise a CI pipeline.
We built an agentic content system at Savage Digital Solutions that does exactly this: it pulls from a git-cloned knowledge base, generates drafts in TypeScript, and publishes to Next.js-powered properties. Before we let it touch the publish button, we needed to answer one question honestly: what is the worst thing this agent could accidentally ship?
The answer was a list. API keys. Database URIs. Internal hostnames. Private IP ranges. JWT tokens. Once we had the list, we built two independent layers to stop them.
Layer One: Exclusion by Construction
