Autonomy within your rules.
Governance is part of the operating system. Noorle checks identity, current capability grants, and policy before a side effect executes—and records the decision.
tickets.read("TKT-482")- Identity
- agent/support-triage
- Capability grant
- read · granted
- Policy
- Allow ticket reads
- Journal
- Read allowed
Allow The connector can fetch the ticket.
tickets.close("TKT-482")- Identity
- agent/support-triage
- Capability grant
- close · granted
- Policy
- Require approval to close
- Journal
- Approval requested
Pause The ticket stays open while the run waits for a reviewer.
tickets.delete("TKT-482")- Identity
- agent/support-triage
- Capability grant
- delete · missing
- Policy
- Skipped after grant refusal
- Journal
- Missing grant recorded
Deny The runtime refuses the call. The ticket stays in place.
Controls live outside the thing they control.
Models propose. Programs order work. Executors carry it out. The runtime owns the decision to admit it.
- Identity
- Resolve who is acting and for whom. Preserve that principal chain through delegated work.
- Capability grant
- Check whether the caller has current authority for this action. A tool’s presence in context is not permission to execute it.
- Policy
- Apply the action’s tier, the surface’s autonomy posture, and hard denial rules before dispatch.
- Journal
- Record the decision, effect, and outcome in an append-only history that outlives the Run.
Choose the room to act.
Set an autonomy posture for the agent and narrow it per thread. The runtime enforces that posture outside the model.
Read-only
Let the agent gather context and inspect information within its granted read access.
Supervised
Let work progress, with actions that require review waiting for a human decision.
Full autonomy
Allow admitted actions to proceed. Intrinsic protections, deny rules, and live grants still apply.
Approval is a durable part of the work.
An agent can ask for a decision. It cannot approve itself.
Pause before execution
The exact intent is recorded, and the Run waits for a human decision. A restart does not erase the pause.
Recheck before resuming
Approval records who resolved the request. Live authority is checked again before the action executes.
Keep the evidence
The journal retains the decision and result alongside model attempts, tool outcomes, and usage.
The boundaries, made explicit.
The details matter when your solution starts acting on real systems.
What happens when a capability is revoked?
Admission uses live grants. Revocation takes effect even when an agent thread still has the tool in its pinned presentation. Approval does not bypass the fresh authority check on resume.
What does full autonomy allow?
Full autonomy changes which actions need human review. It does not override intrinsic protections, hard denial rules, or the requirement for a current capability grant.
Can an MCP Gateway pause for approval?
Gateways do not currently have a trusted human approval path. Requests that would pause are denied. Configure each Gateway’s policy for the actions its audience should be able to perform.
How is execution separated from control?
Plugins, Sandboxes, Computers, and connectors execute admitted work. The control plane owns identity, authority, admission, and the journal outside those executors.
What if an external write has an uncertain result?
Durable recovery uses recorded outcomes. An uncertain external write parks for resolution instead of being repeated blindly. A Gateway’s journal is an audit record, not a replay stream.
Customer data
Read the Privacy Policy for how Noorle handles personal data in Customer Content. See Subprocessors for the providers involved, their roles, and where they process data.