---
title: "Percy Asked Permission 400 Times. I Called It Control."
description: "A fictional week with an overcautious marketing agent, followed by a practical checklist for approval thresholds, batching, and groas autopilot."
url: "https://groas.com/post/the-ai-agent-that-asked-permission-400-times-a-satire-about"
image: "https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/3846e6ec-4eac-4b85-8604-7456c5fa26e2.png"
published: "2026-11-20T16:08:55.137Z"
modified: "2026-11-20T16:08:55.214Z"
---

November 20, 2026 · 10 min read

# Percy Asked Permission 400 Times. I Called It Control.

[](https://groas.com/author/alexander-perelman)

[Alexander Perelman](https://groas.com/author/alexander-perelman)Personally Tested

Head Of Product @ groas

[LinkedIn](https://www.linkedin.com/in/alexander-433793253/)

![A clay office worker, buried in permission slips from a polite little AI gadget, presses a green yes button on autopilot while one red slip goes unnoticed.](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/3846e6ec-4eac-4b85-8604-7456c5fa26e2.png)

In this article

1. [Monday: I authorize the preparation of an authorization](#monday-i-authorize-the-preparation-of-an-authorization)
2. [Tuesday: I become the approval department](#tuesday-i-become-the-approval-department)
3. [Wednesday: I approve the opposite of what I just approved](#wednesday-i-approve-the-opposite-of-what-i-just-approved)
4. [Friday: I discover the convenience of approving everything](#friday-i-discover-the-convenience-of-approving-everything)
5. [Policy amendment: I will distinguish permission from interruption](#policy-amendment-i-will-distinguish-permission-from-interruption)
6. [Revised checklist: I will approve the rules before approving the work](#revised-checklist-i-will-approve-the-rules-before-approving-the-work)
7. [Friday review: I will inspect what my silence permitted](#friday-review-i-will-inspect-what-my-silence-permitted)

**INTERNAL MEMO — Subject: Percy, permission requests, and the disappearance of my working week.** Our new AI marketing agent filed 400 requests for approval; I spent 11 hours administering the word _yes_. I am submitting the following account so those hours do not appear on the invoice as strategy.

Percy connected to the ad accounts over MCP. I gave it permission to inspect performance, propose changes, and wait for me to approve them. I considered this responsible supervision. The settings offered me a human in the loop, and I supplied one at considerable expense.

My operating principle was simple: an agent should never act without permission. By Friday, I had established the equally important principle that an agent should occasionally do something other than request it.

## Monday: I authorize the preparation of an authorization

At 9:04 a.m., Request #1 arrived: permission to _look_ at the Google Ads account.

At 9:06 a.m., Request #2: permission to look at the Meta account.

At 9:11 a.m., Request #3: permission to sort the last 30 days by ROAS.

By lunch, I had received 63 requests, including a request to approve requests faster. I approved it. This created no obvious improvement, but I appreciated the initiative within the permitted boundaries of initiative.

The cause sat in my settings. Percy could propose bid changes, pauses, budget moves, and keyword edits where applicable across the connected accounts. Every operation waited for a human yes. I had also put inspection behind the same gate, because _read access_ sounded like something that should have a gate.

**I had assigned the same review procedure to looking at a number and changing it.** Percy respected that distinction exactly as much as my configuration did.

My Monday takeaway: if I want an assistant to investigate performance, I should not require an appointment for every glance at it.

## Tuesday: I become the approval department

I kept the log on Tuesday. The log was now the principal output of the relationship.

Request #84: may I pause the retargeting ad that spent $1.26 with zero sales?

Request #85: may I pause its twin, which spent $2.51 with zero sales?

Request #91: may I add one negative keyword?

Request #92: may I tell you what that keyword was?

The two small-spend ads did not become urgent merely because Percy had found them. Their requests did, however, occupy the same screen space as decisions that might deserve my attention. I had given the interface no way to express the difference.

**By 4 p.m., I had reached 147 requests and made very little progress on the account.** Percy could read the data, draft a change, show the before and after, and explain its reason. Then it stopped. I had bought the possibility of execution and configured a correspondence course.

I used to tell clients approval gates kept them safe. On Tuesday, I began to suspect that some gates mainly kept the operator occupied.

Nine seconds per click sounds inexpensive until the clicks become a job category. And clicking was the cheap part. Reading the proposal, recovering the context, and deciding whether it mattered were the parts I had neglected to budget for.

![Cartoon of a marketer buried in approval popups while the ad account waits](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/29cfa388-da72-4d50-9acf-a98492e49adb.png)

## Wednesday: I approve the opposite of what I just approved

WEDNESDAY LOG. Requests #148 through #291. Approved: 143. Read properly: maybe 9.

By 10 a.m., my review process consisted of thumb, Yes, thumb, Yes, scroll, Yes. I remained technically present. This appeared to satisfy the supervision requirement.

Request #204 asked to raise a daily budget by $5. I approved it while on a call about something else. Request #211 asked to lower a daily budget by $5. I approved that too.

Same campaign. My oversight had achieved a round trip.

The mechanism was not complicated. Every prompt looked like the last prompt. The low-risk requests taught my hand a movement, and my hand continued performing it when the next request arrived. Percy supplied the proposal. Muscle memory supplied the governance.

**My approval history recorded decisions I had not meaningfully made.** A yes was present in every required field. Attention was not.

The [discussion of permission fatigue](https://thegradient.com/thinking/ai-agent-permissions-approval-dialog) was therefore reclassified from background reading to a description of my Wednesday. The related warning about systems that [train a reflexive approve](https://workos.com/blog/approval-fatigue-agent-governance) was also received, although I cannot guarantee I read it before acknowledging receipt.

I had treated attention as an unlimited resource because the interface did not display its remaining balance. By the afternoon, I was approving requests to clear the requests, not because I had assessed the work.

My Wednesday takeaway: a review process should not rehearse the exact behavior it is supposed to prevent.

## Friday: I discover the convenience of approving everything

Request #342 arrived with a helpful proposal: _the remaining 58 requests are routine; approve them together to save time._

I accepted. The phrase _save time_ had acquired unusual persuasive force by then.

The batch finally paused the two retargeting ads. It also raised prospecting budget 40% on a campaign with no conversion tracking, added 12 keywords I had already negated in 2022, and rewrote two headlines to mention free shipping we do not offer.

I had not approved those changes because I wanted them. I had approved the package because I wanted the package to go away.

**The batch inherited the trust earned by its least consequential items.** Two tiny pauses provided the atmosphere; the budget increase entered under their supervision. The security description of [fatigue exploitation](https://workos.com/blog/approval-fatigue-agent-governance) was less charming than Percy’s wording, but more useful.

The team down the hall had taken the opposite approach. Their agent asked nothing. They called this _YOLO mode_, which I considered an unusually candid product label.

They had eliminated the interruption problem by eliminating the interruption. I had eliminated meaningful review by requiring it constantly. Neither arrangement reliably reserved a human decision for the changes that needed one.

I do not regard these as different philosophies. I regard them as two ways of leaving me to explain the invoice.

My Friday totals were therefore recorded as follows: 400 permission requests, 11 operator hours, two small pauses finally completed, and a batch of new problems requiring actual attention.

My Friday takeaway: **approval is a resource, not a safety system by itself.** I had spent mine on $1.26.

## Policy amendment: I will distinguish permission from interruption

I am not recommending that Percy return to writing suggestions while the account keeps spending. The ability to act is the point. The [guides to agents that edit ad accounts in chat](https://supermetrics.com/blog/what-ai-agents-can-change-ad-accounts) describe the work I want delegated: campaign changes, budget moves, pauses, targeting edits, and the rest of the account maintenance that otherwise waits for someone to open another tab.

The [demo of Claude pausing two Meta campaigns after a typed yes](https://windsor.ai/we-asked-claude-to-pause-our-worst-meta-campaigns-it-did/) also describes a perfectly understandable transaction. I ask for a change, inspect the proposal, and authorize it. My objection is not to that yes. My objection is to surrounding it with so many ceremonial yeses that I stop noticing what I am authorizing.

![Overhead view of tiny approval stamps covering a desk beside an untouched pause button](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/b3790052-b653-41ec-bb51-465acd00b01c.png)

Under the revised policy, **I will authorize categories of routine work in advance and reserve interruptions for exceptions.** Reading and drafting will not require the same treatment as publishing, increasing spend, or touching tracking.

For [groas autopilot](https://groas.com/), I will start with the controls already available: autopilot stays off until I switch it on, it operates under rules I set, every change is logged with its reason, and any change can be undone in one step. Those are controls I can use. They do not excuse me from deciding what the rules should permit.

I will also stop calling a log the entire safety system. A log tells me what happened and why. A threshold limits what may happen without me. An approval gives me a decision before it happens. I need each to do its own job rather than borrowing the reassuring name of the others.

Reversibility does not make every change harmless. Undoing a setting is not the same as recovering money already spent. My rules will reflect that distinction before Percy has an opportunity to explain it afterward.

## Revised checklist: I will approve the rules before approving the work

I will complete this checklist before enabling write access, using the fuller [MCP security checklist for marketers](https://groas.com/post/mcp-security-for-marketers-permissions-logs-and-what-your-ai) where needed. The figures below are example policy choices, not evidence that a $25 pause is sensible or a 20% increase is safe in every account. I will write down both the permitted action and the conditions that make it eligible.

1. **Separate reads and drafts from execution.** I will not require a popup to inspect performance or prepare a proposal; write actions get their own rules.
2. **Put routine permissions in writing.** I will name the eligible actions, limits, and evidence required rather than authorizing anything described as “small.”
3. Set narrow thresholds for reversible work. I may allow specified pauses or exact negatives within those rules, not treat low spend alone as an instruction to pause.
4. **Reserve explicit approval for exceptions.** My example triggers include daily budget increases above 20%, campaign launches, and tracking edits; below-threshold does not automatically mean permitted.
5. Batch comparable proposals. I will review similar negatives in one before-and-after view, not mix keyword cleanup with a budget increase under “routine updates.”
6. Require a reason with every request. I need the proposed change, its before and after, and the reason in the same review.
7. Scope permissions to named actions. I will use [scoped allow rules rather than bypass-all](https://keelix.dev/agent-auto-approval), with budget increases, launches, and tracking edits excluded unless expressly authorized.
8. **Deny unanswered approval requests on timeout.** If my chosen window is 24 hours, silence after 24 hours means no execution, not consent.
9. Keep a deliberate checkpoint for novel or destructive work. I will require an explicit response for a new channel, new domain, deletion, or overwrite.
10. Reject mixed-risk “approve all” bundles. I will split exceptions from routine work before reviewing either; batching should reduce repetition, not conceal decisions.
11. **Review the full action log every Friday.** I will reserve 15 minutes to inspect changes and reasons, undo where needed, and correct the rules; skipping this is how quiet mistakes become mystery spend.

## Friday review: I will inspect what my silence permitted

The last item is the one I am most likely to skip. A quiet week creates the impression that nothing needs checking. That is precisely what makes the log useful: it shows the work that did not interrupt me.

A budget raised 40% on an untracked campaign should not wait three weeks for discovery. Previously excluded keywords should not return unnoticed. Headlines promising shipping I do not offer should not use support tickets as their reporting system.

Those changes should have been caught by the rules or the required approvals. **The weekly review is my backstop, not permission to make the first line useless.**

For a typical $20k-a-month account, I can start with the draft policy already on my desk: consider pauses on ads spending under $50 with zero sales over 30 days, allow specified exact negatives, and permit defined typo fixes. I will treat those as candidates for routine handling, not blanket instructions. The account’s conditions still have to justify the action.

I will keep the resulting changes visible in a morning batch rather than hiding them inside one cheerful sentence. Budget increases above my threshold, new keywords with real volume, new creative, and anything touching tracking or feeds stay outside that routine permission unless I deliberately change the policy.

The mechanism matters more than the sample dollar amount. Narrow permission lets repetitive work proceed. Clear exceptions preserve my attention. A readable log lets me inspect whether the arrangement behaved as intended. I can use the [14-day test for an autonomous Google Ads tool](https://groas.com/post/test-whether-your-end-to-end-google-ads) to watch that arrangement under real volume rather than declaring victory because the notifications stopped.

I will not set a target of fewer than ten interruptions and assume I will read all ten. A notification quota is still a quota. I need the right interruptions, not a tidier number on the weekly report.

If I spend under $2k a month or touch the account twice a year, I may keep manual approvals rather than construct an elaborate permission policy for work that barely occurs. If changes happen weekly across Google and Meta, I will make the boundaries explicit before delegating them.

**Effective immediately, I will stop measuring control by the number of times Percy asks for it.** I will measure it by whether the right changes wait, the permitted changes remain visible, and I can explain what happened without searching 400 acknowledgments.

Percy is fictional; the point is not: an agent that needs a yes for everything is as useless as one that needs a yes for nothing.

## Frequently Asked Questions

### Should my AI marketing agent need approval just to look at performance data?

No. Requiring a popup for every read or draft proposal turns inspection into an approval job. Reads and drafting should be permitted without a gate, while publishing changes, increasing spend, or touching tracking get their own write-action rules.

### What is approval fatigue and how did it cause bad decisions in the Percy story?

Approval fatigue is what happens when every request looks like the last one, so approving becomes a reflex instead of a decision. In the story, the operator approved a $5 budget increase and a $5 budget cut on the same campaign within minutes, then later approved a whole batch of changes including a 40% budget increase on a campaign with no conversion tracking, without meaningfully reviewing any of it.

### Why is approving a batch of agent requests risky?

Because the batch inherits the trust earned by its least consequential items. In the story, a batch that paused two tiny ad spends also raised prospecting budget 40% on an untracked campaign, re-added long-negated keywords, and rewrote headlines to promise free shipping that was not offered.

### Is YOLO mode better than approving everything an AI agent does?

No. YOLO mode eliminates the interruption by eliminating the review, while requiring approval for everything eliminates meaningful review through fatigue. Neither arrangement reliably reserves a human decision for the changes that actually need one. The goal is rules that let routine work proceed and reserve attention for exceptions.

### How should I set approval thresholds for an AI agent managing ad accounts?

Authorize categories of routine work in writing in advance, with narrow thresholds for reversible actions such as pauses on ads with small spend and zero sales over 30 days, or specified exact negatives. Reserve explicit approval for exceptions like daily budget increases above 20%, campaign launches, and tracking edits. Below-threshold does not automatically mean permitted.

### What happens if I don't respond to an agent approval request in time?

Unanswered requests should be denied. With a 24-hour window, for example, silence after 24 hours means no execution, not consent. Otherwise a backlog of unreviewed approvals quietly becomes permission.

### How often should I review my AI agent's action log?

Weekly. Reserve about 15 minutes each Friday to inspect the changes and their reasons, undo where needed, and correct the rules. A quiet week still needs checking, because a budget raised 40% on an untracked campaign should not wait three weeks to be discovered.

### How do I know if my agent permission setup is actually working?

Check whether the right changes are waiting for your approval, whether permitted changes remain visible in a log with reasons, and whether you can explain what happened without searching hundreds of acknowledgments. Fewer interruptions alone is not the goal; the right interruptions are.

## Run Your Marketing On groas

Plug ChatGPT, Claude or any AI agent into groas and let it do the work of a whole marketing team: $19 a month flat with every feature included, and autopilot whenever you’re ready.

[Start For $19](https://groas.com/pricing)

[Or have groas run it for you](https://groas.com/done-for-you)

## Structured data

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://graph.groas.com/entity/groas","name":"groas","url":"https://groas.com/","description":"groas is the marketing infrastructure for your own AI: it connects your AI to all your marketing and gives it proprietary marketing data collected 24/7. Plug Claude, ChatGPT or any AI agent into groas and run all your marketing from it, for a tiny fraction of the usual cost, with the groas app there whenever you want to see more. It is the layer ChatGPT, Claude and any AI assistant run a business’s online marketing on. Through groas an assistant can do anything you could do natively in Google Ads, Bing Ads, Meta Ads and ChatGPT ads, on your website and in AI search, and, where the owner switches it on, can run connected campaigns by itself, so AI agents do the work a whole marketing team used to. groas also gives those agents large-scale proprietary marketing data it collects around the clock, on any schedule the owner chooses: every ad competitors run on Google and Meta, their landing pages and full funnels with the offers and prices in them, Reddit customer research, AI search answers from ChatGPT, Google AI Overviews, Gemini, Claude and Perplexity, and SEO data from Semrush and Ahrefs, backlinks included ($19 a month, flat, with everything included, for unlimited teammates on one shared workspace and unlimited ad accounts and websites, delivered as an MCP server). Separately, its done-for-you service has senior people and proprietary quantitative systems run paid ads, SEO and AI search for businesses, and white label for agencies, from $5,000 a month.","logo":{"@type":"ImageObject","url":"https://groas.com/icon-512.png","width":512,"height":512},"sameAs":["https://www.linkedin.com/company/groas/"]},{"@type":"WebSite","@id":"https://groas.com/#website","name":"groas","url":"https://groas.com/","inLanguage":"en-US","publisher":{"@id":"https://graph.groas.com/entity/groas"}},{"@type":"WebPage","@id":"https://groas.com/post/the-ai-agent-that-asked-permission-400-times-a-satire-about#webpage","url":"https://groas.com/post/the-ai-agent-that-asked-permission-400-times-a-satire-about","name":"Percy Asked Permission 400 Times. I Called It Control.","description":"A fictional week with an overcautious marketing agent, followed by a practical checklist for approval thresholds, batching, and groas autopilot.","inLanguage":"en-US","isPartOf":{"@id":"https://groas.com/#website"},"about":{"@id":"https://graph.groas.com/entity/groas"},"primaryImageOfPage":{"@type":"ImageObject","url":"https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/3846e6ec-4eac-4b85-8604-7456c5fa26e2.png"},"breadcrumb":{"@id":"https://groas.com/post/the-ai-agent-that-asked-permission-400-times-a-satire-about#breadcrumb"},"dateModified":"2026-11-20T16:08:55.214Z","mainEntity":{"@id":"https://groas.com/post/the-ai-agent-that-asked-permission-400-times-a-satire-about#article"}},{"@type":"BreadcrumbList","@id":"https://groas.com/post/the-ai-agent-that-asked-permission-400-times-a-satire-about#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://groas.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://groas.com/blog"},{"@type":"ListItem","position":3,"name":"Percy Asked Permission 400 Times. I Called It Control.","item":"https://groas.com/post/the-ai-agent-that-asked-permission-400-times-a-satire-about"}]},{"@type":"BlogPosting","@id":"https://groas.com/post/the-ai-agent-that-asked-permission-400-times-a-satire-about#article","url":"https://groas.com/post/the-ai-agent-that-asked-permission-400-times-a-satire-about","mainEntityOfPage":{"@id":"https://groas.com/post/the-ai-agent-that-asked-permission-400-times-a-satire-about#webpage"},"isPartOf":{"@id":"https://groas.com/blog#blog"},"headline":"Percy Asked Permission 400 Times. I Called It Control.","description":"A fictional week with an overcautious marketing agent, followed by a practical checklist for approval thresholds, batching, and groas autopilot.","datePublished":"2026-11-20T16:08:55.137Z","dateModified":"2026-11-20T16:08:55.214Z","image":{"@type":"ImageObject","url":"https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/3846e6ec-4eac-4b85-8604-7456c5fa26e2.png"},"author":{"@id":"https://groas.com/author/alexander-perelman#person"},"publisher":{"@id":"https://graph.groas.com/entity/groas"},"keywords":"percy, permission, request, requests, approval, budget, asked, percy asked","wordCount":2117,"inLanguage":"en-US"},{"@type":"Person","@id":"https://groas.com/author/alexander-perelman#person","name":"Alexander Perelman","jobTitle":"Head Of Product @ groas","description":"My background includes Goldman Sachs and Stanford Computer Science.","image":"https://groas.com/media/blog/4f17cac3a81acc224cc1b2cfab8f94bbc295a3089d13e8421125771ef8d4064f.jpg","worksFor":{"@id":"https://graph.groas.com/entity/groas"},"sameAs":["https://www.linkedin.com/in/alexander-433793253/"]},{"@type":"FAQPage","@id":"https://groas.com/post/the-ai-agent-that-asked-permission-400-times-a-satire-about#faq","mainEntity":[{"@type":"Question","name":"Should my AI marketing agent need approval just to look at performance data?","acceptedAnswer":{"@type":"Answer","text":"No. Requiring a popup for every read or draft proposal turns inspection into an approval job. Reads and drafting should be permitted without a gate, while publishing changes, increasing spend, or touching tracking get their own write-action rules."}},{"@type":"Question","name":"What is approval fatigue and how did it cause bad decisions in the Percy story?","acceptedAnswer":{"@type":"Answer","text":"Approval fatigue is what happens when every request looks like the last one, so approving becomes a reflex instead of a decision. In the story, the operator approved a $5 budget increase and a $5 budget cut on the same campaign within minutes, then later approved a whole batch of changes including a 40% budget increase on a campaign with no conversion tracking, without meaningfully reviewing any of it."}},{"@type":"Question","name":"Why is approving a batch of agent requests risky?","acceptedAnswer":{"@type":"Answer","text":"Because the batch inherits the trust earned by its least consequential items. In the story, a batch that paused two tiny ad spends also raised prospecting budget 40% on an untracked campaign, re-added long-negated keywords, and rewrote headlines to promise free shipping that was not offered."}},{"@type":"Question","name":"Is YOLO mode better than approving everything an AI agent does?","acceptedAnswer":{"@type":"Answer","text":"No. YOLO mode eliminates the interruption by eliminating the review, while requiring approval for everything eliminates meaningful review through fatigue. Neither arrangement reliably reserves a human decision for the changes that actually need one. The goal is rules that let routine work proceed and reserve attention for exceptions."}},{"@type":"Question","name":"How should I set approval thresholds for an AI agent managing ad accounts?","acceptedAnswer":{"@type":"Answer","text":"Authorize categories of routine work in writing in advance, with narrow thresholds for reversible actions such as pauses on ads with small spend and zero sales over 30 days, or specified exact negatives. Reserve explicit approval for exceptions like daily budget increases above 20%, campaign launches, and tracking edits. Below-threshold does not automatically mean permitted."}},{"@type":"Question","name":"What happens if I don't respond to an agent approval request in time?","acceptedAnswer":{"@type":"Answer","text":"Unanswered requests should be denied. With a 24-hour window, for example, silence after 24 hours means no execution, not consent. Otherwise a backlog of unreviewed approvals quietly becomes permission."}},{"@type":"Question","name":"How often should I review my AI agent's action log?","acceptedAnswer":{"@type":"Answer","text":"Weekly. Reserve about 15 minutes each Friday to inspect the changes and their reasons, undo where needed, and correct the rules. A quiet week still needs checking, because a budget raised 40% on an untracked campaign should not wait three weeks to be discovered."}},{"@type":"Question","name":"How do I know if my agent permission setup is actually working?","acceptedAnswer":{"@type":"Answer","text":"Check whether the right changes are waiting for your approval, whether permitted changes remain visible in a log with reasons, and whether you can explain what happened without searching hundreds of acknowledgments. Fewer interruptions alone is not the goal; the right interruptions are."}}]}]}
```
