Skip to content
Blog

Default deny, in plain English

Every Titan deployment starts with one rule: deny everything. Why that is the friendly choice, and how you get from there to agents doing real work.

A hand plugging a hardware security key into a laptop

A new Titan deployment has a single rule in its policy. It is called deny-all, and it does what it says. An agent connected to that deployment can ask to do anything it likes, and every request is refused.

That sounds unhelpful. It is the opposite: it means the only things your agents can do are the things somebody decided they should.

Three answers

Titan decides every call an agent makes through its tools, at the moment it makes it. A rule can say one of three things: allow the call, deny it, or make it wait for people to approve it. Rules match on what is being called, a capability or every capability in a toolkit, and can be narrowed to particular workspaces, environments, agents and kinds of side effect.

When more than one rule matches, the strictest wins. Deny beats require approval, which beats allow, whatever order the rules are in. And when no rule matches at all, the answer is no.

Every decision, whichever way it goes, is written to the Agent Ledger with the reason behind it, so a refusal is never a mystery to the people who run the agent.

Why no is the right default

The alternative is a policy that allows everything except what you thought to forbid. That policy is only as good as your imagination on the day you wrote it. Agents are inventive, tools are added every week, and the capability nobody thought about is exactly the one an agent will find.

Under default deny, a forgotten case fails safe. The agent is refused, the refusal is recorded with its reason, and someone can decide whether it should have been allowed. The cost of a missing rule is a question, not an incident.

Writes wait for a person

Some calls change things in other systems: posting a message, updating a record, issuing a refund. In Titan, an allow rule alone never runs a write to an organization’s tool. It needs a rule that names who may approve it.

An approval rule sets how many approvals a call needs, how long a request may stay open, and whether the person who asked, or the person the agent acts for, is barred from approving it. An approval covers one call with its arguments. It is not a standing pass.

While a call waits, the agent waits with it. Nothing runs until enough approvers have said yes, and a request nobody decides in time simply expires.

Signed, every time

When you save a policy, Titan compiles it, checks it against your organization’s own policy layers and refuses anything it can’t enforce, rather than accept a rule that would quietly be ignored. Then it signs the policy and publishes it. An edit made against a policy someone else has since changed is refused instead of overwriting their work, and every revision is kept, so you can compare two and roll back.

The policy deciding your agents’ calls is always one you can point to, with a revision and a signature.

Suggestions, never surprises

Starting from deny-all means the early days include refusals. Titan helps you past them without loosening the default. When an agent keeps being refused for the same thing, Titan can suggest a rule that would allow it, drawn from what the ledger actually recorded: the deployment, the agent, the capability and the operation. Never from an agent’s own claims, an argument value or a tool’s output.

A suggestion is only ever a proposal. It is shown as a change against your current signed policy, it only adds rules, and an added allow can never lift an existing deny. If you want to see what a rule would do first, you can run it watch-only, where Titan records what it would have decided without changing any decision. You accept it, or you don’t. Nothing allows itself.

In one line

Your agents do what you said, wait for people where you said, and nothing else. Everything they asked for and didn’t get is on the record, so you can decide, deliberately, what to allow next.

Written by Hexel Studio. Questions about anything here? Talk to us.

An engineer replies in a dayTalk to us Docs, SDK and APIStart building