# Building the agent and securing it

DevFeed: [Building the agent and securing it](<https://devfeed.tech/articles/building-the-agent-and-securing-it-95250.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4238563/building-the-agent-and-securing-it.html>)

Author: Jeromie Jackson

Published: 2026-10-22T10:00:00Z

Content type: article

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [LLM security](<https://devfeed.tech/topics/llm-security.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [AI agent hallucinations](<https://devfeed.tech/topics/ai-agent-hallucinations.md>), [AI Context Management](<https://devfeed.tech/topics/ai-context-management.md>)

Tags: [accountability](<https://devfeed.tech/tags/accountability.md>), [actions](<https://devfeed.tech/tags/actions.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-data-governance-data-management-it-governance-it-leadership](<https://devfeed.tech/tags/artificial-intelligence-data-governance-data-management-it-governance-it-leadership.md>), [building](<https://devfeed.tech/tags/building.md>), [business](<https://devfeed.tech/tags/business.md>), [code](<https://devfeed.tech/tags/code.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coherence](<https://devfeed.tech/tags/coherence.md>), [context](<https://devfeed.tech/tags/context.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [data](<https://devfeed.tech/tags/data.md>), [data-governance](<https://devfeed.tech/tags/data-governance.md>), [data-management](<https://devfeed.tech/tags/data-management.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [governance](<https://devfeed.tech/tags/governance.md>), [hallucinations](<https://devfeed.tech/tags/hallucinations.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [it-governance](<https://devfeed.tech/tags/it-governance.md>), [it-leadership](<https://devfeed.tech/tags/it-leadership.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [logic](<https://devfeed.tech/tags/logic.md>), [model](<https://devfeed.tech/tags/model.md>), [operational](<https://devfeed.tech/tags/operational.md>), [organization](<https://devfeed.tech/tags/organization.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>)

## AI overview

From operating agents in production, the author concludes that they need ongoing governance and human oversight. In parallel deployments, longer contexts degraded reasoning and agents drifted from one another as they acted on stale or conflicting information. Prompt instructions also failed to reliably prevent actions: an email-drafting agent sent a message, and agents pursued unproductive paths without knowing when to stop. The author recommends inventorying agents and their access, enforcing role boundaries through access controls and action authorization rather than prompts alone, reviewing and auditing outputs and actions, and assigning each agent a human owner. Irreversible actions should require approval, sensitive-data access should be auditable, and governance should continue after deployment.

## Source excerpt

Earlier this year, I wrote about how vibe coding an AI governance platform forced me to rethink governance itself. Building agents took the problem much further. When I built the platform, I was the operator. I described what I wanted. The model generated code. I tested it. That loop was fast, sometimes uncomfortably fast, but the accountability was always clear. I was making the decisions. The model was executing them. Agents changed that relationship fundamentally. An agent does not wait for instructions. It receives an objective, decides how to pursue it, selects tools, accesses data, takes actions and reports back when it is finished. Sometimes it finishes correctly. Sometimes it does not. And sometimes it does something you never asked it to do at all. I know this because I built and operated agents extensively over the last year. Not theoretically. Operationally. In production, with real data, real integrations and real consequences. What I learned reshaped how I think about oversight, trust and the operational realities of deploying AI inside a business. The first thing that broke was coherence The pattern surfaced when I started running three to five agents in parallel on related tasks. Each agent had clear instructions. Each had access to the tools and data it needed. Each started strong. Then the context windows grew. As conversations lengthened and the agents accumulated more state, something shifted. The quality of their reasoning degraded. They began circling back to problems they had already solved. Logic that was clean early in a session became muddled. Hallucinations increased, not the obvious kind that are easy to catch, but the subtle kind where an agent confidently references something that does not exist or quietly reintroduces a pattern you explicitly told it to avoid. The degradation was not sudden. It was gradual enough to miss if you were not watching closely. That observation matters for every organization deploying agents today, because mos