Sign in Start free
Overview Capabilities Agents Gateways Workflows Trust
Gateways

The right tools. The right front door.

Compose built-ins, plugins, connectors, and published Workflows into a dedicated MCP endpoint—with its own audience, authentication, and autonomy policy.

Gateway · support-ops live request preview
Bound resources42 tools
●Ordersbuilt-in
▲Refund policyplugin · v2
◇Zendeskconnector
▣Customer onboardingWorkflow · v3
composereferences, not copies
● active support-ops dedicated MCP endpoint
access
OAuth 2.1 · API keys
policy
supervised
presentation
adaptive
resolvelive for this caller
MCP clientauthenticated
principalservice:returns-bottoken audience · support-ops
tools/list3 discovery toolsAdaptive · 42 bound
tools/callorders.lookupallow · read
tools/callrefunds.issuedeny · would ask
current bindings on every request access scoped to this gateway every outcome journaled
The object

A boundary, not a bag of tools.

A Gateway is a customer-composed MCP surface. It points at resources you already own, then gives that exact composition a name, an endpoint, an audience, and a policy.

The resources remain reusable. Change one Gateway without cloning a connector, forking a plugin, or changing what an Agent can use.

gateway:support-opsfour decisions
01
Composition

Which built-ins, plugins, connectors, and Workflows appear.

what
02
Endpoint

A dedicated MCP address clients can configure once.

where
03
Access

Public, private, or private with dynamic client registration.

who
04
Autonomy

Read-only, supervised, or full—plus explicit tool-level pins.

may
one operational object · independently activatable
Compose the surface

One endpoint can speak for the whole platform.

Attach only the resources this audience needs. The Gateway holds references to the live resources, so each one keeps its own credentials, limits, execution boundary, and version.

01 · built-ins●

Platform tools

Files, web search, HTTP, knowledge, browser, sandboxes, and the rest of the MCP-exposed first-party set.

maintained by Noorle
02 · plugins▲

Your code

Versioned, permissioned plugins run inside a strict in-process sandbox and expose their declared tools.

customer logic · isolated runtime
03 · connectors◇

External systems

REST, OpenAPI, and remote MCP services with encrypted credentials and managed OAuth where supported.

the systems you already use
04 · Workflows▣

Published work

Attach named, versioned Workflows alongside individual tools when the operation itself is the interface.

durable work, exposed as a tool
Trust by composition

Different callers deserve different doors.

The Gateway—not the individual caller—is the unit of trust segmentation. When two audiences need different capabilities or autonomy, create two Gateways over the same underlying resources.

Composition is cheap. Keep trust legible instead of hiding a second permission system inside one sprawling endpoint.

shared resources
◇ordersconnector
▲refund policyplugin · v2
▣return intakeWorkflow · v5
partner-supportOAuth
Read the order. Start a return.

6 tools · supervised · Discovery

partners
internal-returnsAPI key
Inspect, refund, and reconcile.

14 tools · full · Direct

trusted automation
same connectorseparate endpointseparate policy
Identity before tools

The caller shapes the surface.

Noorle resolves the Gateway and caller before it builds tools/list. Credentials are checked against the requested Gateway, and authenticated callers receive their own stable, isolated workspace where a capability needs one.

Anonymous callers never inherit a shared workspace. Tools that cannot be isolated safely without identity are withheld from that caller’s surface.

request admissionsupport-ops
AuthorizationBearer ••••••••••••resource · gateway:support-ops
01Resolve Gatewayactive · current config
02Verify callerservice:returns-bot
03Derive workspacegateway + principal
04Build tool surfacecaller-safe · live
principal isolatedtoken audience matched
01 · public

No authentication

Anyone with the endpoint can connect. Use only when anonymous access is the intended boundary.

workspace-dependent tools may be withheld
02 · private

Known clients only

Authorize connected apps through OAuth 2.1 or issue API keys for machine-to-machine access.

identity-bound surface
03 · private + registration

Clients can onboard

OAuth 2.1 dynamic client registration lets compatible clients register before authorization.

default · connected apps and API keys still work
Autonomy on an unattended surface

When nobody can approve, ask becomes deny.

A Gateway owns a policy independent of every Agent. MCP calls have no trusted human approval path today, so a decision that would pause elsewhere ends safely: the call is denied, never quietly allowed.

gateway policy · support-ops● enforced
default posture
Read-onlyreads only
Supervisedselected actions may run
Fullallow within the hard floor
exposed toolriskpolicyoutcome
orders.lookupreadlevelallow
tickets.commentactallow autonomousallow
refunds.issueactalways askdeny
customers.eraseacthard floordeny
incoming callrefunds.issue · $184.00
interactive decisionwould ask a human
MCP outcomedenied · journaled
pin beats allowRead-only cannot be liftedthe hard floor always wins
01

Read-only

Only Read-tier tools run. An allow list cannot lift an action above this level.

02

Supervised balanced

Reads run; explicitly selected actions run; everything else denies.

03

Full

Tools run by default, still bounded by intrinsic protections and the administrative denylist.

Tool presentation

Forty tools should not feel like forty tools.

Composition decides what can be reached. Presentation decides how those tools appear to the connecting client. Pick a mode explicitly or let Adaptive choose from the current bound-tool count.

Gateways resolve this surface live per request. Agent conversations use a different lifetime: their tool snapshot is pinned to the thread.

tool presentationconfigured · adaptive
Adaptiverecommended

Direct for a compact catalog; Discovery when the bound surface reaches 30 tools.

Direct

Expose every bound tool separately to the client.

Discovery

Expose three tools that search, describe, and execute the catalog progressively.

Unified

Expose one natural-language dispatcher for the cleanest client surface.

current bindings42 tools
Adaptive threshold30+
presented surfaceDiscovery · 3 tools
Journal · gateway:support-opstrace · 01J8QF
09:17:03.041GatewayResolved42 current tools
09:17:03.046PrincipalResolvedservice:returns-bot
09:17:03.052PresentationSelectedadaptive → discovery
09:17:08.114OperationStartedorders.lookup
09:17:08.117GateDecisionallow · gateway policy
09:17:08.300OperationCompletedsuccess · 186 ms
09:18:12.802OperationStartedrefunds.issue
09:18:12.806GateDecisiondeny · unattended
09:18:12.809OperationCompleteddenied · 7 ms
sessionless is normalfailures close truthfully
Every request, accounted for

Stateless protocol. Accountable operation.

The Gateway resolves current bindings, identity, presentation, and policy when the request arrives. A change is visible on the next request—there is no server-held MCP session quietly preserving an old surface.

  • 01
    Live resolution

    Unbind a tool or deactivate a Gateway and the next request sees it.

  • 02
    Truthful completion

    Successes, denials, timeouts, and in-band tool failures all leave outcomes.

  • 03
    Attributable usage

    Gateway, caller, capability, latency, and cost stay connected in the journal.

The journal is the audit record for Gateway calls—not a replay stream for rerunning them.

The platform nouns

One substrate. Different jobs.

Keep the object model small: a Capability defines an action; a Gateway defines an MCP boundary; an Agent is a durable principal; a Workflow is published, durable work.

01 · action

Capability

What can happen, including its execution and intrinsic limits.

bound into surfaces →
02 · MCP boundary

Gateway

Which resources an audience can reach, and under which access and autonomy posture.

the page you are on
03 · principal

Agent

Who reasons, remembers, and acts across durable threads and interfaces.

meet Agents → 04 · published work

Workflow

A named, versioned Program whose Runs can wait, resume, and be operated.

explore Workflows →

Give every audience the right front door.

Choose the tools · name the boundary · set the rules

Start free Explore capabilities