TL;DR: Agentic AI shifts the security problem from content risk to effect risk because model outputs can now trigger actions, costs, and data movement, according to LEVO. The control gap is no longer model quality alone but scoped permissions, approvals, logging, and data boundaries for systems that can act.
Editorial analysis by NHI Mgmt Group, based on content published by LEVO: “What is AI Security?”.
Key questions
Q: What breaks when an AI system can take actions, not just generate content?
A: The control model breaks because content review no longer contains the risk.
Q: Why do agentic AI systems create more security risk than standard chatbots?
A: Agentic systems can turn model output into action, which means a bad instruction can affect code flow, tool use, and downstream state.
Q: How do organisations know if agentic AI governance is actually working?
A: Look for three signals: access decisions tied to task context, complete audit records linking agents to datasets, and rapid revocation when scope changes.
Practitioner guidance
- Define capability tiers for every agent Separate read, write, and effectful actions so approvals only apply where the system can actually change state or move data.
- Put AI gateway controls at the model boundary Enforce input and output policy, schema checks, and budget limits before prompts reach tools or external services.
- Minimise context and retrieval sources Allow only approved knowledge sources, redact secrets and personal data, and keep retrieval scoped to the task at hand.
Bottom line: Agentic AI changes the primary security question from whether output is safe to whether the system is allowed to act safely.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Effect risk is now the right governance frame for agentic AI. The decisive issue is no longer whether outputs are accurate enough for users to trust them. It is whether a system can change state, move data, or spend money under a delegated authority that was never designed for autonomous action. Practitioners should govern agents as effectful systems, not as smarter chatbots.
A few things that frame the scale:
- Only 23% of IT leaders were very confident in their organisation's ability to manage security and governance for GenAI deployments, according to a 2025 Gartner survey of 360 IT leaders.
A question worth separating out:
Q: What is the difference between securing AI and using AI for security?
A: Securing AI protects models, data, and pipelines from attack. Using AI for security applies machine learning to improve detection, prioritisation, and response. Both matter, but they solve different problems. A mature programme needs controls for the AI system itself, not only AI-assisted security operations.
👉 Read our full editorial: Agentic AI turns content risk into effect risk, not just bad output