Documentation on AgentCore Gateway for integrating external APIs and services.
AI agents call agentcore_gateway to retrieve information from AWS AgentCore MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool is narrowly scoped to deliver documentation/guidance content. It is a reference resource that enables users to understand how to integrate APIs, not a tool that itself executes code, performs write operations, calls external services, or handles financial transactions.
From the tool's definition Tool provides 'Documentation on AgentCore Gateway' — it retrieves and presents information about API integration capabilities rather than executing integrations, modifying configurations, or invoking external services.
Attacks that exploit this kind of access
Documentation on AgentCore Gateway for integrating external APIs and services. It is categorised as a Read tool in the AWS AgentCore MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS AgentCore MCP Server MCP server in PolicyLayer and add a rule for agentcore_gateway: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches AWS AgentCore MCP Server. Nothing to install.
agentcore_gateway is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the agentcore_gateway rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for agentcore_gateway. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
agentcore_gateway is provided by the AWS AgentCore MCP Server MCP server (weiwarren/agentcore-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →