API key sprawl

Every model provider, tool, and service issues keys. They get copied into .env files, hard-coded for a quick test, pasted into a Slack thread, committed to a repo, baked into a container image. Nobody tracks the full set, so nobody can rotate or revoke confidently.

Why it matters

LLM infrastructure concentrates keys — a gateway or an MCP server config often holds many at once — so one exposed component leaks a lot. And model-provider keys map directly to money: a leaked key is immediate unauthorized spend. Secret scanning, a real secrets manager, and short-lived credentials are the countermeasures; exposed LLM gateways are where this project most often expects to see the failure.