cd /news/ai-agents/sponsor-workos-let-agents-use-your-t… · home › topics › ai-agents › article
[ARTICLE · art-166716] src=workos.com ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

[Sponsor] WorkOS: Let Agents Use Your Tools Without Giving Them Free Rein

WorkOS released Airlock, an authorization layer for agentic software, in early access. Airlock evaluates every agent tool call against the agent's runtime intent and then allows, denies, or routes it to a human, replacing pre-granted roles and scopes with static policies plus per-call runtime checks. WorkOS says policies live in one place and apply across every agent and team, with every request and verdict logged for security review.

by read2 min views2 publishedNov 10, 2026
[Sponsor] WorkOS: Let Agents Use Your Tools Without Giving Them Free Rein
Image: Workos (auto-discovered)

Manual approval

Safe, until you stop reading the prompts you're approving.

Airlock

Airlock is the missing authorization layer for agentic software. Every call an agent makes is evaluated against its intent and then allowed, denied, or sent to a human.

Least privilege requires hard-coding permissions. An agent's job is unknown until runtime, so teams settle for one of two extremes.

Fast, until the agent does something you can't undo.

With Airlock, you don't have to compromise.

No roles to assign, no scopes to pre-grant. Airlock authorizes agent access to all of your tools and integrations.

The task defines what the agent is allowed to do.

“Find last month's duplicate charges and refund them.”

The agent calls your tools and integrations as it works.

search · charges, last 30 days

refund · $1,240 in duplicate fees

delete · customer record

Every call is judged against the intent and your rules.

Static rules set fixed limits on your integrations. Runtime rules judge what static rules can't. What should agents be allowed to do?

Agents can read repos, review code, and comment on PRs.

They can merge a PR when CI is passing, it has an approved review, and the change is small in scope.

Anything touching auth, billing, or migrations needs sign-off from the code owner.

Never push to main directly, and never delete branches.

Static Policies Always in effect

Runtime Checks

Judged per call

Check the PR first: CI must pass, has a review, and the diff is small.

Must be less than 200 lines and edit minimal files within a single domain.

Changes touching auth, billing, or migrations must be approved by the code owner.

Use Airlock to manage authorization for all your agents in one place, wherever they run. Airlock connects coding agents, custom harnesses, and AI teammates to every tool they need, without changing how they operate.

Policies live in one place and apply to every agent, on every team. Change a rule once and it takes effect across the organization.

Every request and every verdict is logged, so security has a complete record of what agents actually do.

Airlock is available in early access. Request access and tell us what you're building.

── more in #ai-agents 4 stories · sorted by recency
── more on @workos 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/sponsor-workos-let-a…] indexed:0 read:2min 2026-11-10 · —