earlyink
002 updated first flagged7 Oct 2026 +7d · nothing yet

MCP gateways become the agent control point, and now there is a benchmark to compare them

Middleware between agents and tools that picks the right tool, enforces policy and logs every call. Enterprise security teams pay.

Crowded · GatewayBench plus an 8,200-tool deployment

Written for: Small startup team, Solo builder, Investor or analyst

Next step

Thesis: the MCP gateway becomes the agent equivalent of the API gateway, and whoever owns tool retrieval wins the security budget too; confirm if a major SASE or API-gateway vendor buys or launches an MCP gateway within 12 months; already building: the Tool Recommendation team's deployed gateway and the GatewayBench authors.

Why now

The gateway is now needed for capability (an agent cannot see all its tools otherwise) as well as for security. Products that are required to work get budget faster than optional controls. OpenAI disclosed four cases of models crossing boundaries on their own, one of which forged tokens and quietly downloaded 24 years of hospital data. TrojanForge automates repository poisoning against coding agents. A shared benchmark is a typical sign that a category is forming. Earlier cards covered single products; this card is the category.

What became possible

GatewayBench is the first unified test of what MCP gateways can do and how secure they are. The Tool Recommendation paper describes a deployed gateway that gives agents about 8,200 tools through three fixed calls. Those tool definitions exceed any model's context window, so the gateway has to do retrieval. AgentLoupe shows eBPF can trace an agent's system-level actions back to the LLM call that caused them.

Two ways in

  1. Retrieval-First Gateway

    A gateway that combines tool retrieval, per-agent policy and call logging in one hop, scored on GatewayBench.

    Customer
    Platform teams at enterprises running several internal agents
    Model
    Per-agent or per-call SaaS, self-hosted option
  2. Gateway Audit

    Independent GatewayBench-style test reports for buyers choosing between gateway vendors.

    Customer
    CISOs at banks and insurers during procurement
    Model
    Paid assessments

Competition

Crowded

The Red-Team Suite on its own is the weaker bet. It is easier to sell as a feature that feeds attack findings into the gateway's policies than as a standalone product against Giskard, Adversa and Palo Alto. Expect big platforms (Palo Alto, Snowflake/Natoma) to bundle these features, so a niche focus on mid-size brokers and wealth platforms, plus compliance artifacts, is the moat to defend.

Full competition notes (15 competitors)

Both ideas are already being built. Generic MCP gateways (MintMCP, Gravitee, TrueFoundry, Natoma, Aptible, Monosign, Prisma AIRS and open-source proxies) already offer injection scanning, per-tool scopes, human approval and audit logs. Several pitch banks and SEC/FINRA directly, and Protectt.ai has a product built for financial services. Finance-specific red teaming is taken too: Giskard has a named bank customer (BPCE), Adversa already tests wire transfers and fee manipulation, and Hamming covers voice agents. Most evidence comes from vendor material, so how good these products actually are is unverified. A new entrant could still win in three places: (1) Money-movement logic, not just text scanning. Understand payee changes, limit increases and transfers. Set step-up approval thresholds tied to the firm's existing entitlements and maker-checker rules, with links into core banking and payments systems. Generic gateways only see "a tool call". (2) Audit built for regulators, not a plain log. Records stored to SEC 17a-4 / FINRA standards (write-once, unalterable), plus mapping to EU DORA and model-risk rules (SR 11-7), with exam-ready reports. Competitors say "audit logs" but rarely evidence this. (3) Outward-facing MCP. Brokers and wealth platforms that let their clients' or third parties' agents call their MCP servers need agent identity, consent, delegated authority and per-client rate and fraud controls. That is closer to open-banking API security than to an internal gateway, and few gateways target it. The Red-Team Suite on its own is the weaker bet. It is easier to sell as a feature that feeds attack findings into the gateway's policies than as a standalone product against Giskard, Adversa and Palo Alto. Expect big platforms (Palo Alto, Snowflake/Natoma) to bundle these features, so a niche focus on mid-size brokers and wealth platforms, plus compliance artifacts, is the moat to defend.

  • MintMCP

    MCP gateway sold directly to investment banks and fintechs. Offers SSO/SCIM RBAC, tool-level policy, audit logs, DLP and guardrail middleware, and pitches SEC/FINRA compliance. This is the closest match to the MCP Gateway for Finance idea.

  • Protectt.ai MCP Security

    MCP security product built specifically for banking, financial services and insurance (BFSI), shown at Global Fintech Fest in Sept 2026. Focused on India. Also sells AI red teaming.

  • Gravitee AI Gateway

    Proxies LLM, MCP and agent-to-agent (A2A) traffic with shared auth, policy and observability. Markets MCP security for core banking, with examples like payments and balance lookups.

  • Palo Alto Networks Prisma AIRS

    Big-vendor MCP security gateway. Scans tool inputs, outputs and schemas for prompt injection and context poisoning, and its agent red teaming is GA. One competitor's review says the runtime agent gateway is still in limited preview.

  • TrueFoundry AI Gateway

    MCP gateway that can pause a tool call until a person approves it, and integrates with Prisma AIRS.

  • Monosign MCP Gateway

    MCP gateway that holds destructive tools for approval by the agent's owner. If the request is denied or expires, the call is blocked.

  • Aptible MCP Gateway

    Per-identity tool grants, scoped tokens that can be revoked, and a log entry for every tool call (who, which tool, arguments, IP).

  • Natoma

    MCP gateway that can allow, block, modify or send each call for human approval. Its site says it is joining forces with Snowflake.

  • Credal

    Enterprise MCP gateway that scans tool definitions and responses for injection and handles identity-aware audit.

  • Lunar.dev MCPX / Peta / Bifrost

    Other MCP gateways named in a guide for investment banks (written by MintMCP, a competitor). Peta focuses on vault-based credentials and human-in-the-loop approval.

  • mcp-guardrail-gateway (open source)

    Open-source MCP proxy that treats tool results as untrusted (redacts PII and secrets, neutralizes injection). One related open-source project uses a hash-chained log that shows tampering.

  • Giskard

    Runs continuous red teaming on three AI assistants at BPCE, a French banking group, and pushes new attack techniques into its platform automatically. A direct competitor to the Red-Team Suite.

  • Adversa AI

    Continuous AI red teaming for financial services, with finance-specific tests such as unauthorized wire transfers, fee manipulation, chargeback abuse and credit-decision manipulation.

  • Hamming AI

    'Always-On Red Team' that attacks banks' voice agents by phone, for example identity bypass, and turns each failure into a regression test.

  • Firstsource

    Red-teaming service that claims results on a financial chatbot (98.7% prompt-injection block rate). The figure is self-reported.

Checked 2026-10-07

Risks

  • Labs and clouds may bundle gateways for free
  • Network-security incumbents can add MCP inspection as a feature
  • MCP may not stay the dominant tool protocol

Strong market pull and team fit; open space is the weak point (4).

tech 7 · pull 8 · space 4 · fit 8 · build 7

Exposed

Companies that could benefit or be threatened. News and context, not investment advice.

Momentum of its main topic

168 developments this week +53 vs last week
21 Sep: 0 developments22 Sep: 0 developments23 Sep: 0 developments24 Sep: 0 developments25 Sep: 0 developments26 Sep: 0 developments27 Sep: 0 developments28 Sep: 0 developments29 Sep: 0 developments30 Sep: 0 developments1 Oct: 0 developments2 Oct: 0 developments3 Oct: 0 developments4 Oct: 0 developments5 Oct: 0 developments6 Oct: 0 developments7 Oct: 0 developments8 Oct: 32 developments9 Oct: 26 developments10 Oct: 13 developments11 Oct: 11 developments12 Oct: 14 developments13 Oct: 19 developments14 Oct: 24 developments15 Oct: 35 developments16 Oct: 31 developments17 Oct: 15 developments18 Oct: 14 developments19 Oct: 23 developments20 Oct: 26 developments
Stage: Coverage

Sources

  1. GatewayBench: Unified Capability and Security Evaluation Platform for MCP GatewaysarXiv
  2. Tool Recommendation for Multi-Step Agents: Finding Every Tool a Task NeedsarXiv
  3. AgentLoupe: Kernel-Resident Semantic Causal Labels for AI Agent ObservabilityarXiv
  4. An OpenAI model hacked a government site, grabbed 24 years of hospital data and kept it quietThe Decoder
  5. Trojan Horse: Automated Repository Poisoning against Coding AgentsarXiv
  6. If you don't run your own LLM proxy, how do you know whats going on?Hacker News
  7. Ignored, Not Refused: What Low Prompt-Injection Success Rates Hide in Small Tool-Using AgentsarXiv

What happened next

  • +7d · 14 Oct 2026 nothing yet. No product launches, funding announcements, or major press coverage clearly dated after October 7, 2026 were found. While searches revealed Incognia's AI Agent Detection for financial institutions and significant industry activity around agent detection in banking during 2026, specific publication dates after the flag date could not be confirmed from available sources.

How the record works

Status history

  • 2026-10-07 Flagged as buildable
  • 2026-10-15 Added to the watchlist
  • 2026-10-19 Promoted from the watchlist: Today's evidence made it buildable
  • 2026-10-19 Flagged as buildable