Topic starter
19/08/2026 3:30 pm
TL;DR: Claude Fable 5 can turn vulnerability discovery into an API call, but Ory argues the real control question is how to authorise the next move safely and deterministically. For agentic systems, probabilistic approval layers create governance ambiguity, not assurance, because runtime access decisions must be in-loop, explicit, and auditable.
Editorial analysis by NHI Mgmt Group, based on content published by Ory: “Claude Fable 5 can find your vulnerabilities. What authorizes its next move?”.
Key questions
A: Security teams should authorize tool calls at the point of execution, not merely trust a model-shaped instruction.
Q: Why are probabilistic classifiers a problem for agent authorisation?
A: Probabilistic classifiers are a problem because authorisation needs repeatable decisions, not guesses about likely intent.
Q: What breaks when an AI agent can choose its own attack path at runtime?
A: Static permissions and human-paced approval models break first.
Practitioner guidance
- Define action-level authorisation boundaries Map which agent actions require explicit pre-execution approval, which can be policy-authorised in-loop, and which must never be delegated to runtime discretion.
- Separate classifier output from final control decisions Use probabilistic detection or ranking only as advisory input, while the allow or deny decision remains deterministic and policy-based.
- Log every agent decision with policy context Capture the action requested, the policy inputs evaluated, the decision outcome, and the tool or API invoked so the control path is auditable.
Bottom line: AI agent governance now depends on deterministic runtime authorisation, not on probabilistic confidence that a proposed action is safe.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
19/08/2026 4:13 pm
Probabilistic approval layers create governance ambiguity, not assurance: When an AI agent can decide its next action at runtime, a score-based or classifier-led approval model cannot guarantee repeatable control outcomes. The same request can be treated differently depending on context drift, tool path, or model interpretation. That makes auditability weak and delegation boundaries hard to defend. Practitioners should read this as a control-design problem, not a model-risk footnote.
A few things that frame the scale:
- 40 percent of financial and software companies have already deployed agentic AI systems, and deployments are expected to double by 2028.
A question worth separating out:
Q: How should organizations approach the governance of AI agents?
A: Organizations should adopt a governance framework that incorporates continuous visibility, adaptive IAM practices, and stringent policy-based controls. This ensures that all agent actions are tracked, authorized appropriately, and assessed for compliance.
👉 Read our full editorial: Deterministic authorisation for AI agents is now a governance issue