AWS AgentCore Gateway Policy Only Gates MCP Tools, Leaves resources/read Always Allowed

rahulladumor · reddit · 2026-10-20

A Reddit post reads the AWS docs to show that AgentCore Gateway's Cedar policy engine, even in ENFORCE mode, only evaluates MCP tools (tools/call and filtered tools/list). MCP prompts and resources — prompts/list, prompts/get, resources/list, resources/read, resources/templates/list — are always allowed regardless of policy mode; inbound auth is the only gateway check described for them.

Why it's easy to miss

Test: with a lowest-privilege token and ENFORCE on, call resources/templates/list then resources/read on a sensitive URI; if content returns, Cedar isn't the protection.

Options: disable resources/prompts on the MCP server if unneeded; authorize inside the server using user-bound outbound credentials rather than shared gateway role credentials; or use a gateway REQUEST interceptor (docs don't confirm it covers resources/read — test it). Non-MCP targets (Lambda, API Gateway, OpenAPI, Smithy) aren't affected. The author notes this is doc-derived, not tested.

Original post →

More from coding & agent

coding & agent channel →