Security1 publisher2 min readPublished
Akeyless ships a runtime veto on AI agent actions its own permissions would allow
Akeyless has made Agentic Runtime Authority generally available. It judges each agent action against the task the agent was given, and blocks a database delete or a bulk export even where the agent's credentials permit it.
The Watch · Security desk

What happened
- Akeyless has made Agentic Runtime Authority generally available, a control layer that evaluates AI agent actions in real time and blocks the ones that violate policy before they execute.
- The layer runs on the same brokered access path as Akeyless SecretlessAI, which keeps credentials out of agents by provisioning a short-lived identity directly on the target system.
- Akeyless names the July 2026 Hugging Face incident as its demonstration that an agent acting unexpectedly or under manipulation escalates impact at machine speed.
Compiled by The WatchSomething wrong?How this is made
Why it matters
- constraint Policy reach stops at the broker. Any agent that holds a long-lived token and connects to a system directly performs actions this layer never sees, so the deployment question is credential inventory.
- decision Someone has to author per-task intent policy, and the material does not say how the evaluator fixes a task boundary. A wrong verdict halts a production workflow.
- capability Action-level logging tied back to the triggering human, application, or agent gives an incident reviewer a named initiator for a prompt-injection session instead of a shared service account.
- precedent Vendors can now sell agent runtime control against a named 2026 incident whose mechanism has not been published. The vendor's own summary sets the bar for that pitch.
Intent enforcement sits above the role- and attribute-based rules an identity team already runs [2]. The evaluator compares what the agent is doing against the task it was assigned and stops the action before it executes [3]. Akeyless's worked example is an agent told to summarize sales data, prevented from deleting a database or moving large volumes of data out, even though its underlying permissions allow both [4]. The material does not say how the evaluator establishes that boundary, and it does not say what happens to a legitimate workflow the policy reads as out of scope [21].
The reach of that check is set by the brokered access path. Runtime Authority runs on the same brokered path SecretlessAI already uses, where the Akeyless Gateway provisions a short-lived identity directly on the target system, including legacy and on-prem targets [6][7]. Actions that never traverse that broker are not evaluated [17]. An agent holding its own long-lived token and connecting directly is outside the policy decision point entirely.
"Humans and machines will continue interacting with critical systems, so having a central point of access control and attribution only matters more over time," said Oded Hareven, CEO of Akeyless [16].
The scale number attached to the launch belongs to the platform. Akeyless says the same identity platform already secures over 220 billion machine identity interactions for Fortune 500 organizations, now applied to the AI agent as a new identity class [11]. No agent-specific volume is disclosed [19].
For the case that credentials are no longer the control point, Akeyless offers the July 2026 Hugging Face incident, cited as the demonstration that impact escalates at machine speed when an agent acts unexpectedly or is manipulated [9]. The reference runs to one clause. There is no mechanism, no victim scope, and no account of what the agent actually did [18]. One vendor invoking one incident tells you what Akeyless is selling against; it does not establish that identity teams have settled on the same reference case.
The operational half of the release is more checkable. The Agentic Access Dashboard gives a live view of active agent sessions with immediate termination, and new investigation capabilities show why a session was blocked [12]. Enriched events forward to Splunk, Datadog, and Microsoft Sentinel [13]. Every action is logged and traced back to the human, application, or agent that triggered it [14].
New integrations cover Claude Enterprise, OpenAI Codex, and Amazon Bedrock AgentCore [10]. Akeyless states that an agent with no stored credential has nothing to steal and nothing to leak [8]. No pricing is stated, and no independent testing of the intent evaluator is reported [22].
What to watch
- A mechanism-level account of the July 2026 Hugging Face incident from Hugging Face or from any responder, which would let buyers test the case Akeyless builds on it.
- Native action-level policy hooks in Claude Enterprise, OpenAI Codex, or Amazon Bedrock AgentCore, which would make an external broker optional.
- Independent testing of the intent evaluator against prompt-injected agents, measuring both bypasses and blocked legitimate workflows.