Composio
QuotaGuard puts two fixed outbound IPs onto a Composio API key's allowlist at the connectivity layer, so you can restrict every key by network origin without changing where you host your agent. Trusted by developer and platform teams securing AI-agent and automation infrastructure at production scale since 2013.
Composio allowlists each API key by IP, and it recommends configuring that restriction on the keys your agents use. A tool-call to backend.composio.dev from an address that is not on the key's allowlist returns a 403, even when the credential is valid. Cloud platforms like Render, Railway, Heroku, Fly.io, and AWS Lambda rotate outbound IPs on every deploy and restart, so the allowlist breaks the next time your app moves. The common fallback is to create a key with no IP restrictions, which works from anywhere and gives up the protection entirely.
- Two-Minute Setup: Add your QuotaGuard connection URL as the QUOTAGUARDSTATIC_URL environment variable in your app. Configure your HTTP client to proxy outbound calls to backend.composio.dev. Paste your two static IPs into the key's allowlist at dashboard.composio.dev/~/settings/ip-allowlist.
- Keeps Every API Key Restricted: A fixed egress means you never take Composio's unrestricted-key fallback. Each key your agents use can carry an IP allowlist, and it stays two entries long through deploys and restarts, so a leaked key has nowhere to work from.
- Built for Agent Tool-Calling and MCP: Works for standard tool-calling, MCP, and toolkit traffic to Composio. The same two IPs also clear allowlist checks on sibling AI services like OpenRouter and Datadog.
- Multi-Platform Support: Works whether you host on Heroku, Render, Railway, Fly.io, AWS Lambda, Vercel, Netlify Functions, Kubernetes, or a direct VPS. The same QuotaGuard configuration applies; set the env var in your hosting platform's settings.
- Production-Grade Reliability: A load-balanced pair of static IPs with automated failover. Tool-calls stay consistent through deploys, restarts, and infrastructure migrations. Both IPs go on the key allowlist, and traffic routes through whichever responds first.
- Shield for Regulated Agent Data: For SOC 2, PCI-DSS, or HIPAA-bound flows where an agent moves regulated PII through a toolkit, QuotaGuard Shield uses SSL passthrough so QuotaGuard never decrypts the data moving between your app and Composio.
Allowlist note: The restriction is per API key, so you can keep a tighter IP allowlist on high-privilege keys without touching every key at once. If you run entirely without key IP restrictions, you do not need a static IP, but the moment you turn the restriction on, a rotating cloud egress makes it impossible to maintain.