MoEngage turns 400 private APIs into permission-scoped agent tools
AWS and MoEngage describe how MoEngage used AgentCore Gateway to expose roughly 400 private REST APIs as permission-scoped tools for agents while keeping the services inaccessible from the public internet. The production system applies Cedar policies and routes requests through private connectivity, while agents authenticate with SigV4 and discover tools through descriptions rather than fixed names. MoEngage estimates the approach saved about six months of platform engineering work and reduced API onboarding from days to hours, although those savings have not been independently verified.
The case study offers a production-scale pattern for giving AI agents access to large numbers of private enterprise APIs without exposing public endpoints or maintaining separate MCP servers for every team.
This post was co-written with Nikhil Kumar and Shakir Khan from MoEngage.
When engineering teams start building AI agents, the capabilities those agents need usually already exist as internal APIs. Campaign creation, segment queries, delivery stats. The challenge isn’t building new functionality. The challenge is making hundreds of private APIs safely reachable by agents without exposing them to the public internet, without giving models control over identity, and without flooding context windows with hundreds of tool definitions.
MoEngage, the agentic customer engagement platform that more than 1,350 consumer brands use to deliver personalized experiences across push, email, in-app, SMS, WhatsApp, and RCS, faced exactly this problem. Behind the product sit roughly 400 internal REST APIs, built by 25 engineering teams, running in private virtual private clouds (VPCs) across seven AWS Regions. MoEngage isolates these APIs regionally to meet data residency commitments and doesn’t expose them to the public internet. The capability the agents needed was already running in production. Making it reachable, safely, was the hard part.
In this post, we walk through how MoEngage used AgentCore Gateway, a capability of Amazon Bedrock AgentCore, to turn those private APIs into permission-scoped agent tools. The approach saved MoEngage an estimated six months of platform engineering effort, and onboarding a new API now takes hours instead of days. No product team wrote Model Context Protocol (MCP) server code, no networking was provisioned per integration, and no public endpoint exists anywhere in the path.
#MoEngage#Amazon Bedrock AgentCore#AgentCore Gateway#Amazon VPC Lattice#Cedar#Model Context Protocol#SigV4#AWS IAM