Skip to content

Agent gateway ​

An issued agent can call its tools through the DutyGraph gateway at POST /api/mcp/agent. The gateway is a narrow, optional enforcement adapter for supported MCP tool paths. It governs only the calls routed through it. It does not replace the company's identity and access management (IAM) or the controls in its business systems.

What the gateway checks ​

Before each call, the gateway checks the agent's credential:

  • the dga_… credential exists, is not revoked or suspended, and has not expired;
  • the agent's status is issued and its end date has not passed;
  • the credential matches the hash of the issued manifest.

Then, for the call itself:

  1. Status and expiry. An expired agent, or one whose event has ended, is blocked under AGT-01 or AGT-10. A suspended or revoked agent is blocked.
  2. Scope. The scope must be one of the agent's issued scopes, or the narrower scope it was issued instead. A scope removed or refused during review is blocked, with the rule that removed it.
  3. Tool and scope match. The tool must be the catalog's gateway tool for that issued scope.

The gateway does not run the evaluator again. It does not recheck the owner's current holdings on each call. It checks the agent against what was issued.

What the gateway records ​

Every checked call writes an activity row: time, agent, tool, scope, allowed or blocked, the reason code and, for a block, the rule. Call arguments are not stored. A blocked call returns the scope, the rule text and the attestation that set the limit.

The row records what the gateway saw. It is not proof that every action the agent took was observed.

Five control properties ​

PropertyWhat it meansStatus
Scope allowlistingOnly issued scopes can be called through the gatewayBuilt, for routed calls
Lifecycle enforcementRevoked, suspended, expired and event-ended agents are blockedBuilt, at the gateway
Per-action human approvalA person approves a single call before it runsNot built in the gateway. It exists only where a runtime has its own approval setting.
Activity recordingEach routed call is recorded with its outcomeBuilt, for routed calls
Target-system enforcementThe business system itself refuses access the agent was not grantedNot DutyGraph's. It belongs to your IAM and business systems. Integrations are Planned.

WARNING

No per-action approval gate. The runtime control table on the issue screen lists "Ask before supervised calls" with the note "Native approval or the DutyGraph gateway approval gate". The DutyGraph gateway approval gate is not built. Where a runtime has its own approval setting, the builder export maps Ask first to it. DutyGraph does not confirm that the runtime applies it.

Credentials ​

Each issued agent gets its own credential (dga_…). It is shown once at issue and stored only as a hash. It is bound to the agent, its manifest hash, its issue record and its end date. Revocation by IAM or Internal Controls ends it at once.

Lifecycle limits ​

  • Revocation and expiry block calls. Built.
  • Owner departure does not. Marking the owner as left in DutyGraph does not suspend their agents or credentials. Revoke each agent by hand. Automatic suspension is Planned.

What the gateway does not cover ​

  • Calls an agent makes some other way, for example with its own credentials straight to a business system.
  • What the business system did with an allowed call. In the sample companies, the business systems behind the gateway are Simulated, and an allowed call returns sample data.
  • Joining identity-provider and target-system logs to the agent identity. This is Planned.

INFO

Status. Built: the credential check, status and expiry checks, the scope and tool check, revocation and the activity record, for calls routed through the gateway. Simulated: the business systems behind the gateway and the agent runtime in the sample companies. Not built: a gateway approval gate for single calls. Planned: owner-departure suspension, target-system integrations and joined identity and system logs. DutyGraph does not host or run agents.

Source: gitbook/product/governance/agent-gateway.md in the DutyGraph repository.

DutyGraph. Pages label each feature Built, In review or Planned.