What Passport Found in 3 Weeks of AI Agent Traffic

Agentic development expands credential risk by allowing tools and subprocesses to make runtime-selected network calls using secrets inherited from environment variables, keychains, configuration files, and credential helpers, making static secret inventories incomplete. In a three-week experiment using Postman Passport, the author observed 22 distinct credentials across 33 requests to 18 hosts despite identifying only four entries in a project’s .env file, illustrating the difference between where secrets are stored and where they travel. Key findings included credentials embedded in URL query parameters, which are more likely to persist in logs and histories; a single API key shared by separate programs, preventing selective revocation; credentialed requests with no identifiable client; and agents sending tokens to third-party Model Context Protocol servers, creating delegation and token-replay concerns. The account argues for replacing copied, reusable secrets with granular, holder-bound access references mediated by a secure proxy, while recommending runtime traffic inspection, per-consumer credentials, regular MCP audits, and process-level attribution where needed. It also reports that using a Context Graph API reduced agent search-related tool calls, tokens, latency, and costs, suggesting that better retrieval can reduce unnecessary subprocesses and credential-bearing network activity, though it does not eliminate essential authenticated calls.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.