DEV Community

tercel
tercel

Posted on

Consolidating Governance Across MCP, HTTP, CLI, and A2A

Most teams already have multiple ways to reach the same operations:

  • REST / HTTP APIs
  • CLIs and scripts
  • internal RPC or message‑bus flows
  • a2a integrations via SaaS tools
  • now: MCP or other agent tool protocols

Each surface tends to evolve its own auth, ACL, and logging story.

That’s painful even before you add AI agents. Once agents are involved, inconsistent governance becomes a hard blocker.

A more durable architecture is to consolidate governance in a protocol‑neutral capability runtime, and let all surfaces become adapters.

Define capabilities once

Create a runtime‑owned catalog where each capability has:

  • a stable ID
  • an input/output schema
  • an owner and risk classification

Backends implement the behavior, but the runtime owns the contract.

Attach governance at the capability layer

Instead of:

  • API gateway policies here
  • service‑level ACLs there
  • custom checks in CLIs
  • broad API keys for agents

…attach:

  • identity + role rules
  • approvals
  • environment constraints
  • additional guards

to the capability itself.

The runtime enforces those rules for every call.

Make protocols into adapters

Adapters for HTTP, CLI, MCP, a2a, etc. should:

  • authenticate in their own context
  • map calls into capability invocations with identity + metadata
  • send them through the runtime
  • map results back

The actual governance (schemas, ACLs, approvals, audit) is shared.

Standardize evidence

Because the runtime sees all invocations, it can emit:

  • structured events (who did what, via which surface)
  • consistent trace IDs and error shapes

That makes incident response and audits tractable even when agents are involved.

Migrate incrementally

You don’t have to flip everything at once.

You can:

  • start with a few high‑risk operations
  • define them as capabilities
  • run them through the runtime for one surface (e.g., CLI)
  • gradually move agent tools and a2a flows over

Each step reduces the number of “islands” with their own policy logic.

For agent use in particular, this consolidation is what lets you say, with a straight face, that agents follow the same rules and leave the same evidence trail as your other callers.

Top comments (0)