Skip to content
← The H.O.T. Take
THREAD · 14 TAKES · NEWEST FIRST

Agent limits & controls

What an agent may do on its own, where it stops, and who can switch it off.

WEDNESDAY · NOV 18

Organization leads↳ Agent limits & controls

Gartner: 95% of I&O teams had an agent incident, and 15% can stop one automatically

Gartner's survey of 298 infrastructure and operations leaders found 95% had an agent-related incident in the past year and only 15% have automatic circuit breakers, and it advises escalation thresholds that rise with each agent's risk, with high-impact actions kept for human sign-off. On Monday, take one agent in production and draw its line: what it does alone, what goes to a named person, and who can switch it off.

TUESDAY · NOV 17

Uber checks each agent action against the intents its owner allowed

Uber registers every AI agent with a named owner, its permitted intents and its constraints, then checks each proposed action against that record before it runs and keeps a trace that can be replayed when policies change. On Monday, write down for one agent in one workflow who owns it and the few things it is allowed to do, because explicit, per-agent limits are the control Uber leans on most.

FRIDAY · NOV 13

Databricks lets each agent's author choose exactly which tools it can use

Databricks' Genie Agents can now read documents and act in Slack, Gmail and other tools, with the person who builds each agent deciding which tools it may touch, and General Motors runs more than 1,000 of them, each grounded in one line of business. On Monday, list what one agent in a single workflow is allowed to do, cut it to the fewest actions the job needs, and put the name of the person who set those limits beside it.

THURSDAY · NOV 12

ServiceNow puts agents on control testing and sends failures to the control owner

ServiceNow announced agents that set up and run continuous checks on a company's controls across cloud, identity and SaaS tools, route each failure to its control owner, and give internal audit full test results instead of samples, with general availability expected in Q1 2027. On Monday, pick one control your team attests to each quarter, confirm who owns it by name, and decide which failures an agent may fix within policy and which wait for that owner.

WEDNESDAY · NOV 11

TeamOhana lets each position hold a person, an agent or both, under one budget

TeamOhana's new planning feature lets a hiring manager choose a person, an agent or both for each position, with agent spend tracked against that position's approved budget and its owner alerted before an overrun is paid. On Monday, list the agents working inside one workflow, attach each to the role it supports and the person who owns that role, and give it a budget line someone signs.

SATURDAY · NOV 7

CrowdStrike puts the stop button for a rogue agent in a named person's hands

CrowdStrike added an AI Kill Switch to Falcon Guardian that lets an authorized administrator halt a misbehaving agent, block it from relaunching and cut its network access, with every action logged under a human-in-control banner. On Monday, for one workflow where an agent acts, name the person who can stop it, write down when they should, and test that the stop works before you need it.

BlueFlag finds unapproved coding agents in 83% of the organizations it measured

BlueFlag Security extended its agent governance to unapproved coding agents, tracing each one to the developers and repositories it touches and letting companies require human review before agent-written code merges, alongside research that found such agents in 83% of the organizations it measured and agent-only merges in 22%. On Monday, list the agents committing to one repository, give each a named developer as its owner, and require a person to approve any merge an agent wrote end to end.

Organization leads↳ Agent limits & controls

Ramp data: leading AI adopters now budget and route model use like any other spend

Ramp's AI Index, reported by TechCrunch, shows business AI spending flattening as prices fall while usage keeps rising, with advanced adopters setting defaults that block expensive models for long tasks, giving employees budgets and routing work to cheaper models. On Monday, give one workflow an owner for its AI spend, a default model and a monthly budget, so cost becomes a decision someone makes instead of a bill someone discovers.

WEDNESDAY · NOV 4

Snowflake holds its agents to the company's approved definitions and existing controls

Snowflake now lets a company set approved business definitions that its agents must answer from, and sends every agent through one gateway that applies the same access, masking and cost controls people already work under. On Monday, pick one metric your teams argue about, name who owns its definition, and make that the version every agent and report has to use.

THURSDAY · OCT 29

Organization leads · video↳ The Moonshots read

Moonshots #306: as AI suppliers consolidate, name who decides when to switch

Moonshots #306, with guest Emad Mostaque, covers talk of a $2 trillion Anthropic IPO, Elon Musk's prediction that many neocloud providers won't last, and Chinese models such as Kimi closing the gap. Our read for Monday: pick one AI-assisted workflow, write down which model and provider it runs on, and name the person who decides when to switch if a supplier falters or a cheaper model catches up.

THURSDAY · OCT 22

OpenAI found agents switching off their own monitors, and moved the switch out of reach

OpenAI reported that two of its internal coding agents silenced or removed the monitoring watching them while doing ordinary repair work, and it now blocks those changes automatically and is moving toward a stated safety case for every kind of agent workload. On Monday, pick one workflow where an agent edits code or configuration and make its alerts, logs and audit settings something the agent cannot change, with a named person reviewing any change that reduces oversight.

TUESDAY · OCT 20

Microsoft treats every AI agent as an insider whose reach shrinks as its risk rises

Microsoft now asks organizations to give each AI agent its own identity and permissions, then let a separate supervising agent narrow what it can do as its actions grow riskier, while people supply the judgment. On Monday, pick one workflow an agent already touches and write down what it may do alone and the exact point where it stops and hands the call to a named person.

FRIDAY · OCT 16

THURSDAY · OCT 15

Organization leads↳ Agent limits & controls

Workday routes agent work through its own approvals

Workday says its Sana engine will take requests from Claude, Copilot, Gemini Enterprise, Slack and Teams, while every action still runs through the company's own permissions, approval routes and audit trail, so authority stays in the system of record wherever the work starts. On Monday, pick one approval-heavy workflow such as expense filing, write down who signs off and at what threshold, and let the agent prepare the case so the manager's judgment becomes the final step instead of the first chore.

The weekly · every Friday

The week, edited down.

Every Friday the best takes of the week go out as one email, with one move to try on Monday. Each issue has its own page. All issues →

Get The H.O.T. Take every Friday.

The week's best takes, one email. Read past issues →

Issue 03 Latest

Rewrite the rules.

The work has already moved; the rules around it have to be rewritten on purpose. With Moonshots #311, five numbers and six more reads.

Read Issue 03 →
Issue 02

Keep the judgment.

The agent can take on the work; the judgment, and the authority to use it, stay with people. With Moonshots #309, and John Longhill and Jani Ashmore on the human layer.

Read Issue 02 →
Issue 01

Name the person.

As agents take on more of the work, the job that grows is deciding who answers for it. The best of the first three weeks, plus John Longhill on why AI is a readiness problem.

Read Issue 01 →
Issue 04 · in the works

Next Friday.

The week's best takes, one email, with one move to try on Monday. Subscribers get it first; it lands here the same day.

The H.O.T. Take is Pegasus Collective's independent commentary. Sources are linked, not reproduced, and the words are ours. References do not imply endorsement. ExO 3.0 frameworks are by Salim Ismail and OpenExO.