Skip to main content
Oathera logo Oathera
Use casesFive stories: no identity, a new identity, impersonation, cloning, and a call outside the boundary. PlatformOathera Agent Enrollment, the Oathera Identity Service and Oathera Agent Enforcement. FeaturesWhat Oathera does for you, grouped by purpose. IntegrationsYour identity provider, your MCP servers, your cloud. SecurityHow Oathera fails closed, and what it doesn't do.
Developer sectionComponents, the identity token, standards and settings. Data sheetsThe buyer and developer data sheets, as PDFs. LearnGuides on giving AI agents an identity of their own. GlossaryPrincipal, sponsor, anchor key, key digest, identity token. SimulatorWatch a stolen token, a replayed proof and a tampered call get refused.
About usThe team and the mission behind Oathera. BlogPosts from the Oathera team. CareersOpen roles at Oathera. ContactTalk to the founders, or become a design partner. LinkedIn ↗Oathera on LinkedIn.
Privacy PolicyHow we handle data. Terms of ServiceTerms for using Oathera. Data Processing AgreementOur DPA for customers. Sub-processorsThird parties we rely on.
Become a design partner

Learn · Enforcement

Operational boundaries for AI agents, enforced at runtime

A config file that lists what an agent should do is a wish. An operational boundary enforced at runtime is a wall. This covers what an operational boundary is, and why where you enforce it matters more than where you declare it.

On this page

  1. What an operational boundary is
  2. Config time vs runtime
  3. How runtime enforcement works
  4. How to set it up
  5. FAQ

What an operational boundary is

An operational boundary is the precise envelope of what an agent may do: which operations it can perform, which resources it can touch, which systems and audiences it can reach, and under what conditions. It is the concrete expression of least privilege for one agent. A good boundary is specific, "read records of type X in system Y", rather than broad, "access the database." The narrower and more explicit it is, the smaller the damage any single agent can cause.

Config time vs runtime

There is a world of difference between declaring a boundary and enforcing one. A boundary written in a config file and read once at startup tells you the intended behavior, but nothing stops the agent from doing more if its credentials permit it. Runtime enforcement means the boundary is checked on every request, at a point outside the agent, right before the action would happen. Config-time declarations describe; runtime enforcement prevents. For agents driven by models that can be nudged off course, only prevention counts.

If the only thing holding an agent inside its boundary is the agent itself, you do not have a boundary, you have a hope.

How runtime enforcement works

Enforcement lives at Oathera Agent Enforcement in front of your tools. On each enforced request Oathera Agent Enforcement verifies the agent's identity and proof, checks the tool and its arguments against its configuration, and asks the Oathera Identity Service for a signed boundary decision. In-scope requests proceed; out of scope requests are refused and recorded. Because Oathera Agent Enforcement sits outside the agent and re-checks every time, every enforced call is checked again, including whether the agent and its principal are still active. Two limits: with the default-deny setting off, which is the default outside production, a tool the server lists but you haven't configured passes through unenforced and is logged; and calls that never reach Oathera Agent Enforcement aren't seen. Combine this with filesystem and network confinement from the sandboxing tools you already run, so the boundary holds even for actions that never reach Oathera Agent Enforcement.

Oathera Agent Enforcement refuses unknown tools, tools you haven't configured when its default-deny setting is on, and arguments outside a tool's allow-list, and the boundary decision checks each agent's list of permitted services.

How to set it up

  1. Derive the boundary from the task. List only the operations, resources, and audiences the agent needs.
  2. Express it as policy. Keep it in version control, reviewed like code; see Oathera's own rules.
  3. Enforce at Oathera Agent Enforcement per request. Verify identity, evaluate the boundary, deny by default.
  4. Confine the runtime. Use your sandboxing tools so filesystem and network access match the boundary too.
  5. Record and expire. Capture boundary decisions and rely on a short identity-token lifetime so authority never outlives the task.

Oathera supplies the identity, Oathera Agent Enforcement enforcement point and the boundary decision. Denying by default is an Oathera Agent Enforcement setting (GATEWAY_DEFAULT_DENY), off by default outside production, and the boundary decision checks the agent's list of permitted services. See features and the use case.

FAQ

What is an operational boundary for an AI agent and how do you enforce one at runtime rather than just at config time?

An operational boundary is the exact set of operations, resources, systems, and audiences an agent is allowed to touch, the concrete form of least privilege for that agent. You enforce it at runtime by routing every agent request through Oathera Agent Enforcement, which verifies the agent's identity and checks the operation before it runs, and by confining filesystem and network access with the sandboxing tools you already run. A config-file declaration only describes intended behavior; runtime enforcement actually prevents out of scope actions.

Why isn't a config file enough to enforce a boundary?

Because nothing checks it after startup. A config read once describes what the agent should do but cannot stop it from doing more if its credentials allow. Runtime enforcement re-checks every request at a point outside the agent.

Where should the boundary be enforced?

Outside the agent: at Oathera Agent Enforcement in front of your resource servers for API calls, and at the runtime sandbox layer for filesystem and network access. Enforcing inside the agent you are trying to constrain is not a real control.

See the use case More guides

← Back to Learn
Oathera logo Oathera

Every AI agent, sworn in. Oathera gives every AI agent an identity bound to the machine it runs on, with a named person who answers for it, and checked every time it acts.

Product

  • Use cases
  • Platform
  • Features
  • Integrations
  • Security

Developers

  • Developer section
  • Data sheets
  • Learn
  • Glossary
  • Simulator

Company

  • About us
  • Blog
  • Careers
  • Contact
  • GitHub

Legal

  • Privacy Policy
  • Terms of Service
  • Data Processing Agreement
  • Sub-processors
© 2026 Oathera Inc. · All rights reserved
Know Your Agent (KYA)

Cookie preferences

We use cookies to run this site and, with your consent, to understand usage and improve Oathera. Strictly necessary cookies are always on; you can choose whether to allow analytics and marketing cookies below.

Read the privacy policy

  • Strictly necessaryAlways on

    Required for the site to work, security, load balancing, and remembering your cookie choices. These cannot be switched off.

  • Help us measure traffic and see how the site is used, so we can improve it. No personal profiles are built.

  • Used to make messages about Oathera more relevant across other sites. Off unless you turn it on.