# A revoked agent permission is a design bug, not a security win

> A new survey finds 78% of companies have pulled permissions from an agent already in production. Revoking after the fact means the job was never written down.

- Type: Opinion
- Published: 2026-11-01
- Author: Sentynel
- URL: https://sentynel.ai/sygnals/a-revoked-permission-is-a-design-bug/
- Language: en

A survey of 300 security leaders reports that 78% of their companies have already pulled permissions from an AI agent running in production. The headline reads as proof that controls work. **It is better read as proof that the permissions were granted before anyone had decided what the agent was for.**

## Revoking is what you do when you skipped scoping

The same survey says 49% found an agent in production with access it should never have had, and only 37% scope an agent's access to the task it was built for. Read together, the pattern is clear: access is granted broadly at launch, then trimmed after something looks wrong.

That is a security team doing cleanup for an operations decision nobody made. The survey was run by a governance vendor, so treat the framing with care. The numbers still describe a familiar habit.

**Agent access in production, security leaders surveyed**

- Pulled permissions from a live agent: 78%
- Found access the agent should never have had: 49%
- Scope access to the task the agent was built for: 37%

Source: Agen.co by Frontegg, The State of Autonomous Agent Governance, 27 October 2026. 300 CISOs and CSOs at U.S. companies with 500+ employees, fielded by Cint, 24–27 September 2026. Vendor-commissioned.

## A permission list is a job description in disguise

When you hire a person you describe the work first: which requests they handle, what they may decide, whom they call when it gets odd. Access follows from that description and nobody gives a new hire the master key to see how it goes.

Agents are usually onboarded the other way round. The integration is connected, the scopes are generous because that is faster, and the job is whatever the agent turns out to do. **The permission set ends up being the only written definition of the role, and it is the wrong one.**

The fix is not a better revocation tool. It is writing the task before granting anything:

- **List the steps the agent performs.** Each step names the system it touches and the action it takes: read, draft, write, send.
- **Grant exactly that.** Read-only where the step only reads. Separate credentials per agent, never an employee's personal login.
- **Write the stop condition.** What makes the agent hand the case to a named person instead of continuing.
- **Review on a calendar.** Compare what the agent was allowed to do with what it did, and shrink the difference.

## A pulled permission is data

If you do have to revoke something, do not stop at the revocation. Ask which step needed that access, who approved it and why the procedure did not say. Every pulled permission is a missing line in the operation's description. Companies that record those lines get tighter every month. Companies that only revoke repeat the cycle with the next agent.

This is also why a governance tool alone does not close the gap. A tool can tell you what an agent can reach. It cannot tell you what the agent should have been doing, because that was never written.

## What a visible operation gives you

In Sentynel's Rodo case, WhatsApp, social and web enquiries were brought into a service operation with a measurable path to resolution. The record reports 82% of live-created enquiries resolved. That figure only exists because every enquiry sits in a defined stage, so what the system is supposed to do is written down before anyone measures it.

**Rodo · first measured window**

- 82%: of live-created enquiries resolved

Source: Source: Rodo operational report, 24 September 2026. The resolution cohort covers 31 August–24 September. Figures describe pipeline records, not all conversations.

An agent placed inside an operation like that inherits its limits from the stages. Access is a consequence of the design instead of a guess.

## A test for this week

Pick one agent you already run. Write one sentence per step it performs, then compare that list with the access it holds today. Every permission without a matching sentence is either a step you forgot to describe or access you should remove. Do that before the next incident does it for you.

## Sources

- https://www.prnewswire.com/news-releases/78-of-enterprises-have-pulled-permissions-from-an-ai-agent-already-in-production-302920128.html
