Approval gates for AI agents
Your coding agent either asks for permission every five minutes, or it can do far more than you think. Usually both, depending on the day you last touched its settings.
After the twentieth prompt you click yes without reading. So you open it up: Bash(*), bypass mode, a GitHub token with write access in an MCP server. From then on nobody checks anything, and the agent reads every issue, web page and calendar invite you point it at.
I run my own agents on my network, my VMs and my cloud accounts, and they never hold the keys. Every change goes through a gate outside the agent: harmless ones pass on their own, a second model reviews the middle ground, and only a short list of things reaches my phone, bound to the exact plan I approve. This playbook is how to build that for your own setup.
WHAT IS IN THE PLAYBOOK
1. Risk tiers instead of yes/no
Four levels (automatic, reviewed by a second model, human, blocked) and a short list of what must always reach a human: deletions, anything exposed to the outside, the control plane itself, cost and bulk changes.
2. The guard can't live in the agent
Why rules in the agent's own config fail once it can edit that config or read untrusted input, and where to put the gate instead: separate credentials, read and write split into two servers, changes only as a proposal.
3. Approve the plan, not the description
Approvals bound to a plan hash, so what you approved is what runs. Applies to infrastructure plans, pull requests and root scripts.
4. A reviewer model that says no
How a second model checks a request against the reason the agent gave, when it may decide on its own, and how it falls back to you.
5. One message per task, not twenty
Bundling all approvals of a task so you decide once with the full picture, plus the audit log that lets you see later who approved what.
6. Templates
Allow and deny sets for Claude Code, MCP configurations with read/write split, a pull request gate, and checklists for your own review.
Format: a guide (PDF and Markdown, in English and German) plus a template repository. Written from a setup in daily use, not from a vendor deck.
49 €
The playbook is not written yet. I will write it if enough people want it. Join the waitlist and I will email you once when it is ready. No newsletter.
CHECK YOUR OWN SETUP FIRST
The free agent-permission-linter (MIT, Python, no dependencies) reads your Claude Code settings, .mcp.json and the configs of Cursor, VS Code and Claude Desktop, and flags what is too broad:
$ python3 agentlint.py
[HIGH ] CC003 .claude/settings.json permissions.allow[0] = 'Bash(python3:*)'
'python3' with arbitrary arguments runs any code; this is Bash(*) in disguise.
It runs locally and sends nothing anywhere.
WHO WRITES THIS
Tobias Zander. CTO since 2011, writing software since school, and running multi-agent systems inside my own companies and in my homelab. More on tobiaszander.de.
IMPRINT
Zandups GmbH, Egelsbacher Straße 79, 63225 Langen (Hessen), Germany. Managing director: Tobias Zander. Commercial register: Amtsgericht Offenbach am Main, HRB 48730. Email: info@tobiaszander.de. Responsible for content under § 18 (2) MStV: Tobias Zander, address as above. We are neither willing nor obliged to take part in dispute resolution before a consumer arbitration board. Full German imprint and privacy policy of this site: Impressum, Datenschutz.
PRIVACY NOTICE (WAITLIST)
Controller
Zandups GmbH, address above, info@tobiaszander.de.
What we process and why
Your email address, the time of signup and confirmation, the language and the channel you came from (the ref parameter in the link, for example ref=cli). Purpose: to tell you when the playbook is available and to measure which channel brings interest. Legal basis: your consent, Art. 6 (1) (a) GDPR. This page sets no cookies and uses no tracking or analytics.
Double opt-in
After you submit the form we send one email with a confirmation link, valid for 7 days. Until you click it, your address is not kept: the signup form stores nothing, the address only travels inside that email. Only after you confirm does the signup reach our mailbox.
Processors
Sending and the signup function run on Amazon Web Services (Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, L-1855 Luxembourg) in the region Frankfurt (eu-central-1), under a data processing agreement (Art. 28 GDPR). Transfers to Amazon Web Services Inc. in the USA cannot be ruled out; AWS is certified under the EU-US Data Privacy Framework. Technical logs of the signup function contain no email addresses. Hosting of this page: see section 3 of the German privacy policy.
Storage and withdrawal
We keep your address until you withdraw consent, and delete it at the latest six months after the waitlist closes. To withdraw, reply to any email from us or write to info@tobiaszander.de.
Your rights
Access, rectification, erasure, restriction, data portability, objection (Art. 15 to 21 GDPR) and the right to lodge a complaint with a supervisory authority, for example the Hessian Commissioner for Data Protection and Freedom of Information (HBDI).