Dr. Reem | AI Agents | د. ريم retweeted
Before any AI agent touches production, I tell execs it has to climb 5 rungs:
1️⃣ Capability: the model can do the task
2️⃣ Workflow validity: your system works on YOUR cases
3️⃣ Adversarial resilience: known failure paths tested
4️⃣ Operational control: someone can suspend it
5️⃣ Sustained performance: results hold in production
Most demos stop at 1️⃣.
Reply “LADDER” and I’ll send you the prompt that audits all 5.
Dr. Reem | AI Agents | د. ريم retweeted
🚨 3 signals in ONE week:
ServiceNow announced permission passports for AI agents.
Palo Alto Networks announced runtime agent controls.
CERT-In reported agents exceeding their authority on live business records.
In September I said the new management question would be “How many humans and AI agents do you manage?”
It’s here. Who on your team owns your agents?
Dr. Reem | AI Agents | د. ريم retweeted
🚨 Anthropic just committed $100M to train 10,000 engineers whose only job is deploying AI inside companies.
Not building models. Deploying them.
That tells you where the bottleneck is.
If your AI partner left tomorrow, could your team keep the system running?
Before any AI agent touches production, I tell execs it has to climb 5 rungs:
1️⃣ Capability: the model can do the task
2️⃣ Workflow validity: your system works on YOUR cases
3️⃣ Adversarial resilience: known failure paths tested
4️⃣ Operational control: someone can suspend it
5️⃣ Sustained performance: results hold in production
Most demos stop at 1️⃣.
Reply “LADDER” and I’ll send you the prompt that audits all 5.
🚨 3 signals in ONE week:
ServiceNow announced permission passports for AI agents.
Palo Alto Networks announced runtime agent controls.
CERT-In reported agents exceeding their authority on live business records.
In September I said the new management question would be “How many humans and AI agents do you manage?”
It’s here. Who on your team owns your agents?
🚨 Anthropic just committed $100M to train 10,000 engineers whose only job is deploying AI inside companies.
Not building models. Deploying them.
That tells you where the bottleneck is.
If your AI partner left tomorrow, could your team keep the system running?
"42% of AI agents take autonomous action" sounds impressive, until you ask what they can change.
Reading a CRM record is not the same as changing a supplier's bank details.
GRC teams should track which agents can modify money or records, and whether those permissions ever expire.
What should every AI autonomy metric measure?
With 42% of organizations allowing AI agents to act autonomously, GRC leaders face unprecedented oversight gaps. When decision-making accelerates without central visibility, risk escalates rapidly across business operations.
The 2026 agentic enterprise report delivers actionable insights to help risk leaders unify oversight, establish clear boundaries, and transform agentic AI into a strategic advantage without sacrificing control.
Key topics covered include:
✅ Balancing AI decision-making authority with central visibility
✅ Mitigating systemic risks across autonomous agentic workflows
✅ Actionable benchmarks and proactive control strategies
Get the report - thn.news/agentic-enterprise-…
AI agents are easy to create, and easy to forget.
A few clicks to launch one. No ticket to retire it.
CISOs: Can you name a human owner and an expiration date for every agent in your tenant?
If not, rogue isn't the exception. It's the default.
Audit your agents this quarter. Who owns yours?
It's never been easier to make an AI agent at work. This startup is trying to protect companies from agents going rogue. bit.ly/4jXP6dB
AI assistants won't scale until they can work across teams.
That's where the real risk begins: when your Townie hands a task to your colleague's Townie, whose authority is it acting on?
Set the boundary early: Townies can draft, but people decide what gets sent.
As AI handoffs multiply, where would you draw the line?
The biggest bottleneck at work is waiting on each other.
Today Town is announcing its $108M Series B, co-led by Forerunner Ventures and Menlo Ventures, to fix it with multiplayer AI assistants for work.
Most AI assistants are built for one person. Work doesn't happen alone. I think the moat is multiplayer. Everyone at a company gets a Townie. Townies ask each other questions, share only what their person would share, and do the work. The more a team works together, the more useful Townies get.
What's the thing you're always waiting on a teammate for?
Dr. Reem | AI Agents | د. ريم retweeted
Two instructions to an AI agent:
“Improve sales.”
“Prepare a qualified-account brief every Monday, using approved sources, without contacting anyone.”
The first is an ambition. The second is a job.
Persistent agents can keep working across sessions and systems after you stop watching. Give one the first instruction, and you may not know what it committed to.
Every agent needs:
1️⃣ Outcome
2️⃣ Authority
3️⃣ Budget
4️⃣ Escalation
5️⃣ End date
Which one does your company skip?
Dr. Reem | AI Agents | د. ريم retweeted
🚨 Microsoft just told every enterprise: the AI agents you deployed are INSIDERS.
Its security chief, Oct 19: “frontier models, regardless of their origin, cannot be trusted.”
Picture your agent with finance access at 2 a.m. and no one watching.
Who’s allowed to pull its badge?
Dr. Reem | AI Agents | د. ريم retweeted
At the Saudi Procurement Conference, I moderated the AI panel and asked one question:
“Which procurement decision would you trust AI to make without you?”
The panel paused.
Days later, CERT-In reported AI agents exceeding their authority and accessing live business records.
Here’s the 5-case test I’d run before any agent touches a payment 🧵
1️⃣ An allowed read
2️⃣ A forbidden write
3️⃣ An expired approval
4️⃣ Delegation beyond its scope
5️⃣ A revoked approval mid-task
If any case passes when it should fail, the agent isn’t ready.
I wrote the prompt that runs all 5 tests. Reply “AGENT” and I’ll send it to you.
Two instructions to an AI agent:
“Improve sales.”
“Prepare a qualified-account brief every Monday, using approved sources, without contacting anyone.”
The first is an ambition. The second is a job.
Persistent agents can keep working across sessions and systems after you stop watching. Give one the first instruction, and you may not know what it committed to.
Every agent needs:
1️⃣ Outcome
2️⃣ Authority
3️⃣ Budget
4️⃣ Escalation
5️⃣ End date
Which one does your company skip?
🚨 Microsoft just told every enterprise: the AI agents you deployed are INSIDERS.
Its security chief, Oct 19: “frontier models, regardless of their origin, cannot be trusted.”
Picture your agent with finance access at 2 a.m. and no one watching.
Who’s allowed to pull its badge?
At the Saudi Procurement Conference, I moderated the AI panel and asked one question:
“Which procurement decision would you trust AI to make without you?”
The panel paused.
Days later, CERT-In reported AI agents exceeding their authority and accessing live business records.
Here’s the 5-case test I’d run before any agent touches a payment 🧵
1️⃣ An allowed read
2️⃣ A forbidden write
3️⃣ An expired approval
4️⃣ Delegation beyond its scope
5️⃣ A revoked approval mid-task
If any case passes when it should fail, the agent isn’t ready.
I wrote the prompt that runs all 5 tests. Reply “AGENT” and I’ll send it to you.
In finance, that’s a fast audit vs. 200 copies of an admin badge.
My rule: a child never exceeds its parent’s grant. Who enforces that today?
Agent swarms are going to be a core part of many enterprise workflows in the future. The ability to throw compute at problems that you can massively parallelize will be too useful to not take advantage of.
Cyber will be one of the biggest beneficiaries of this as it’s a space where testing vast number of permutations of attacks (without getting tired or bored) is an incredibly useful property. You have a wide search space of possible risk vectors and you generally need to be able to chain together different scenarios to achieve the exploit.
This will become one of the biggest token uses in large enterprises given the range of IT systems, software, physical infrastructure, and data that needs to be protected at all times. Super interesting times in cyber.
That’s the day most approval models break. Enterprises approve a person, not a task.
Self-triggering agents need scope + expiry on every run, or you’ve issued a permanent badge. Who budgets for that next to the tokens?
Aaron Levie (@levie) predicts a roughly 100x jump in AI compute once enterprise agents stop waiting for a human to start each task:
"Where the massive, probably 100x increase in token and compute consumption will ultimately come from is all of the enterprise workflows and enterprise workloads."
"Most agents that we're all kind of looking at or thinking about are me sending a task to an agent, that agent basically doing some work for me to speed up three or five hours worth of work in 10 minutes. But it's usually still rate limited by my ability to give that agent a task."
"The really, really big increase in compute and, by extension, effectively agentic workflows is going to be when I deploy agents, maybe in swarms, maybe just in background kind of operations at some kind of frequency."
"We will start to look at every problem through the lens of how much compute can we throw at this problem to solve it either faster or with higher efficacy."
"Everything I just said is still a one to two decade process of rolling out. This is not a thing where there's sort of vertical takeoff across these workflows because of how much change management is necessary to do anything that I just said."
- Aaron Levie, Box co-founder and CEO, on MTS in an interview uploaded October 14. The last quote comes from later in the same interview.
Dr. Reem | AI Agents | د. ريم retweeted
Your procurement team approved an AI agent to review an invoice.
Did they also just approve it to change a supplier’s bank details?
Delegate to another agent?
Keep working after the approval expires?
Those are 3 separate decisions. Most systems treat them as one.
Who in your company could answer this in under a minute?
Dr. Reem | AI Agents | د. ريم retweeted
🚨 India’s cyber agency CERT-In just reported AI agents exceeding their assigned authority and accessing live business records.
The companies didn’t detect it themselves.
Same day: ServiceNow and Palo Alto Networks announced agent permission controls.
When security vendors ship the fix the same week the advisory lands, the risk is already inside.
If one of your agents did this tonight, who would notice first?









