What is protocol pivoting?

Protocol pivoting is server-side request forgery through an AI agent's tools: a tool fetches a URL the agent supplies from inside your network, so whoever steers the agent reaches systems they could not reach directly.

Share

Protocol pivoting is server-side request forgery through an AI agent's tools: a tool fetches a URL the agent supplies from inside your network, so whoever steers the agent reaches systems they could not reach directly.

Why it matters

Agents pass URLs and hostnames to tools constantly, and many MCP servers will fetch whatever they are given. That turns a prompt injection, which normally only changes what the agent says, into network access to internal services and cloud metadata endpoints. Hostname-only checks are easy to bypass with DNS rebinding.

Example

On 6 October 2026 a researcher reported that MCP servers which fetch agent-supplied URLs can be used to reach internal networks (researcher write-up; CVE-2026-14540 per the researcher, not yet on NVD).

How to defend against it

  • Give every URL-fetching tool an egress allowlist, enforced at a proxy outside the tool (checklist).
  • Resolve the hostname first, then block private, loopback and link-local addresses, including 169.254.169.254.
  • Run fetchers in a network-isolated sandbox with no credentials.
  • Log every fetch with the agent session that requested it.

Ambient credentials, indirect prompt injection, MCP gateway.

Sources

From AgentSec Brief, the daily brief on securing agentic AI. Subscribe free at https://www.agentsecbrief.com