Menu

1 / 5

AgentCore Gateway: How MoEngage Turned 400 Private APIs Into Permission-Scoped Agent Tools

DEV Community: aws·mech.app·15 days ago
#BCxlLpGF
#devtoaws#devto#dev#tool#gateway
Reading 0:00
15s threshold

MoEngage runs roughly 400 private REST APIs across 7 AWS Regions. They needed agents to call these APIs without writing 400 MCP servers, exposing public endpoints, or cramming 400 tool definitions into every agent's context window.

Amazon Bedrock AgentCore Gateway solves this by sitting between the agent orchestrator and internal APIs. It reads OpenAPI specs, generates tool schemas, filters tools by Cedar permission policies, and routes calls through Amazon VPC Lattice to private backends. The agent sees only the tools it has permission to use.

This is infrastructure for tool boundaries at scale.

The 400-API Problem

Most agent tool tutorials show you how to wrap one or two APIs in an MCP server. That works until you have hundreds of internal services.

What breaks at scale:

Context window bloat : Sending 400 tool definitions to the agent on every turn wastes tokens and slows planning.

Permission sprawl : Different users need different subsets of tools.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.