Beyond the MCP Gateway

MCP connects. NewCore governs.

An MCP gateway controls the connection, not the identity behind the action.

NewCore provides accountability by asking who the agent is, who it’s acting for, and whether it should be doing this right now.

The traditional MCP gateway

Human
Agent
Token
Resource

The NewCore way

Human
Delegated
Authority
Agent
Tool
Resource
POLICY +
AUDIT
Governance Principles
  • Access scopedAccess scoped to the task, not the agent.
  • Tied to a humanEvery action tied back to a responsible human.
  • AuthorityAuthority that follows the agent across servers, apps, and org boundaries.
  • RevocationInstant revocation at machine speed, including sub-agents and ephemeral workloads.

The MCP Gateway Tax

Access is not governance.

The gateway controls the connection, not the identity behind the action.

Gateways treat agents as application credentials, lean on static keys and coarse scopes, and enforce policy in silos. None of that shows who acted, or under whose authority.

A gateway is effectively a second policy engine. When access rules live in both your IdP and your gateway, they will eventually disagree, and the disagreement will surface as an incident.

MCP Connections
Human
Authority
MISSING
NO DELEGATION
Agentservice token
tools/call
MCP gatewayChecks the tokenALLOW
forwarded
MCP server
MCP server
MCP server

Delegated Authority

Stop treating AI agents like applications.

Give them identity, delegated authority, and accountability.

MCP Gateway

humanapptoken

Gateways see a human, an app, and a token.

humanagentauthority · this task

NewCore sees the whole chain: the human, the agent acting for them, and the authority delegated for a specific task.

Each agent gets only what the task requires, never the full reach of the human behind it, and every grant can be audited and revoked.

How It Works

Identity-governed, from registration to kill switch.

Identity, delegated authority, and runtime enforcement for every agent, across every boundary

  1. 01RegisterPeople, agents, apps, APIs, MCP servers
  2. 02ConnectAuthority bound to an accountable owner
  3. 03BrokerShort-lived, scoped access on demand
  4. 04AuthorizeEvery tool call evaluated at runtime
  5. 05AuditOne record of every decision
  6. 06CutSession, agent, or access path terminated

Comparison Matrix

Where MCP Gateways Fall Short

  • Discover MCP servers/tools
    MCP Gateway
    Yes
    NewCore Agent Guardian
    Yes
  • Authenticate agent
    MCP Gateway
    Yes
    NewCore Agent Guardian
    Yes
  • Validate OAuth token
    MCP Gateway
    Yes
    NewCore Agent Guardian
    Yes
  • Token exchange
    MCP Gateway
    Limited
    NewCore Agent Guardian
    Yes
  • Obtain downstream credentials
    MCP Gateway
    Limited
    NewCore Agent Guardian
    Yes
  • Create and manage agent identities
    MCP Gateway
    Limited(product dependent)
    NewCore Agent Guardian
    Yes(core capability)
  • Establish and manage human → agent delegation
    MCP Gateway
    Limited
    NewCore Agent Guardian
    Yes(core capability)
  • JIT agent identity
    MCP Gateway
    No
    NewCore Agent Guardian
    Yes
  • JIT privilege
    MCP Gateway
    Yes(optional, manual)
    NewCore Agent Guardian
    Yes(automatic + enforce)
  • Cross-boundary identity continuity
    MCP Gateway
    No
    NewCore Agent Guardian
    Yes(core capability)
  • Unified human + agent policy
    MCP Gateway
    No
    NewCore Agent Guardian
    Yes
  • Automatic expiration of delegated authority
    MCP Gateway
    Credential dependent
    NewCore Agent Guardian
    Yes(policy driven)

Get agentic governance

Go Beyond the MCP Gateway

The problem you’re planning for is the one we’ve already solved.

Every identity becomes part of one graph. Every decision runs through one policy plane.

Schedule time with one of our solution engineers to show you how we enable agentic accountability.