Benchmark your AI security readiness for 2027 → [Take the survey]

Benchmark your AI security readiness for 2027 → [Take the survey]

Benchmark your AI security readiness for 2027 → [Take the survey]

//Question

Which AI Runtime Security Tools Work With Existing Agents and Gateways Without a New Proxy?

Posted on 19th November, 2026

Harry

Harry

//Answer

Many do, through one of four integration patterns. “No new proxy” still means some change, such as a gateway setting, an agent hook or an added API call. What changes is where enforcement plugs in, and how much traffic it actually sees.

Integration

What it requires

Important limitation

Existing gateway plugin or hook

Configure the current gateway

Only covers traffic traversing that gateway

Agent or MCP hook

Configure supported agent integration

Coverage varies by framework and tool

Inspection API

Add a call at an existing enforcement point

May require code or configuration changes

Network/identity integration

Connect existing infrastructure

Visibility does not automatically mean tool-call blocking

Before choosing, ask every vendor for two things:

  • Exact deployment steps for your gateway, agents and frameworks: what you configure, where, and who owns the change.

  • Proof that enforcement can’t be bypassed. A gateway plugin protects nothing if an agent holds its own model API key and calls the provider directly. Route egress so the gateway is the only path, find agents with direct credentials, and confirm what happens when the guardrail times out. Then test it: send a prohibited tool call through every route you know of, and check that each one is blocked before execution.

Most teams combine patterns:

  • Gateway plugins for model traffic.

  • Agent hooks for coding agents on developer machines.

  • Network or identity integrations for discovery.

A dedicated MCP proxy still makes sense where no existing chokepoint sees MCP tool calls.

Akto integrates with existing AI gateways, including LiteLLM, Portkey, Kong, Apigee, Envoy, NGINX and Cloudflare. It plugs into the hook systems of Claude Code, Cursor, GitHub Copilot and OpenCode, and connects to Kubernetes, OpenShift and eBPF traffic sources for discovery. Where no gateway sees MCP traffic, Akto MCP Proxy can be added. Teams adding it change only the MCP server URL, and servers and credentials stay the same. See Akto’s agentic AI guardrails.

The right integration is the one every request has to pass through.

Comments