default_policy Explained: allow, block, or conditional
Published November 14, 2026 · Reviewed November 2026 · By the Ingenious AI team
The short answer
default_policy is the single most consequential field in an agent-policy.json file: it is the verdict for every AI agent your agents array does not name. It takes exactly three values. allow lets unnamed agents operate. block refuses them. conditional means contact the owner first — a pause, not a refusal. Everything else in the file is an exception to this one line.
What is a default policy?
A default policy is a fallback rule. Agents arrive under identifiers you may never have seen — the v0.1 registry lists six known agents, and new agents appear constantly. A policy cannot name them all, so the format answers them in advance with one value. Think of it as the sign on the door, while per-agent rules are the named guest list: the guest list overrides the sign for the people on it, and the sign governs everyone else. AgentGate's own published policy uses conditional as its default, with a generic/* rule spelling out what unnamed agents may do after contact.
What each value commits you to
allow commits you to openness with unnamed agents operating under no per-agent terms — no rate limit you set, no data-use terms you wrote — unless you also publish a generic/* rule to bind them. The blog sample pairs an allow default with exactly that discipline in reverse: everyone is welcome, and the one agent the owner objects to is named and switched off. block commits you to silence: the bank sample is a block default with an empty agents list, the shortest useful policy in the format. conditional commits you to answering email. It converts unknown-agent traffic into inbound conversations, which is only a good trade if the owner.contact in your header reaches a person who replies.
How the default interacts with rules
A named rule replaces the default entirely for that agent — the agent reads its rule, not the default. An agent with no rule reads the default, and if a generic/* rule exists, the catch-all is the more specific statement of the owner's intent for strangers. This layering is why the store sample can be welcoming and cautious at once: conditional default, named agents allowed on stated terms, catch-all held to conditional at 10 requests per minute. The worked mechanics of layering are covered in per-agent rules explained and the generic/* guide.
One misunderstanding to avoid: the default is not a dial you set per action. It carries no action lists of its own. If you want unnamed agents to browse but never buy, the default alone cannot say that — a generic/* rule with the right lists says it, as the browse-but-not-checkout guide shows.
Choosing, honestly
Choose block when the honest answer for unknown agents is no — regulated, sensitive, or simply not agent-ready. Choose allow when agent traffic is pure upside for you and you accept unnamed agents on catch-all terms you publish. Choose conditional when the answer is "it depends who is asking" — the most common real answer, and the one that turns your policy from a notice into a negotiation channel. Whichever you choose, remember the spec's standing caveat: the default declares your answer. An agent that never fetches the file will never read it, which is why the ignores-your-policy guide exists.
One last discipline separates a default that works from a default that merely exists: write the reason down somewhere your successor can find it. The value itself is one word in a JSON file, but the reasoning — why strangers are paused rather than refused, why the posture flipped in a given quarter — lives in your change log, your review notes, or the notice field's second sentence. Defaults get re-argued whenever ownership changes, and the owner who inherits a reasoned default defends it or improves it; the owner who inherits a bare value simply re-decides it from nothing, usually under time pressure, occasionally in the wrong direction. The cheapest sentence in your whole policy estate is the one that explains its most consequential word.
Worked example: a clinic network picks conditional, then measures it
Fictional example. Northgate Clinics, a fictional group running 9 clinic sites on one domain, debated block versus conditional for a default. Patient-adjacent content argued for block; the appointment pages argued for a conversation. They published conditional with two named rules — both no, disallowing every listed action for two agents that had scraped their provider directory — and a generic/* rule at conditional, 10 requests per minute. Over the following quarter the contact address received 11 agent-operator enquiries; 4 became written allowances added as named rules, 7 were declined. The default did the sorting: nobody legitimate was silently refused, and nobody at all was silently admitted.
Choosing your default in five checks
- Answer for strangers first. If an agent you have never heard of arrives tonight, what should it be told?
- Check your inbox capacity. Pick
conditionalonly ifowner.contactreaches someone who replies. - Pair allow with a catch-all rule. An
allowdefault plus ageneric/*rule binds strangers to stated terms. - Keep block honest. A
blockdefault with named exceptions is a guest list — maintain it like one. - Revisit on schedule. The default is a decision with a date on it; review it whenever you update
last_updated.
Keep reading
Per-Agent Rules in agent-policy.json, Explained · Permitted vs Disallowed Actions in an Agent Policy · Agent Policy vs robots.txt, Compared · Spec samples · Conformance · Pricing · All guides
Frequently asked questions
What is the difference between block and a per-agent no?
Scope. default_policy block refuses every agent the file does not name. A per-agent rule with allowed set to no refuses one named agent. The blog sample uses the second: an allow default for the world, and one named agent switched off entirely.
Does conditional mean the agent can operate while it waits?
No. Conditional means contact the owner first — the agent should pause and get the owner's agreement before operating. The spec deliberately defines no real-time negotiation protocol in v0.1; the policy declares where the boundary is, and contact happens through the owner contact in the header.
Can I change my default later?
Yes — it is your document. Edit the value, update last_updated, and re-validate. Agents that fetched the earlier version hold a stale copy, which is one reason the review date matters: it tells a returning agent the terms it cached may have moved.
Which default do the published samples use?
All three appear. The bank sample uses block with an empty agents list. The blog sample uses allow with one named denial. The store sample uses conditional with named allowances and a conditional catch-all. AgentGate's own policy also uses conditional.
What if I publish no default at all?
The document is invalid — default_policy is one of the seven required top-level fields. The free validator reports the omission as an error, and agents reading the file have no fallback answer for unnamed agents, which is precisely the gap the field exists to close.
Generate a policy — free · Validate a policy · What an agent access policy is