AWS API MCP Server Security Policy Bypass Under Investigation
An issue has been reported in the AWS API MCP Server where a failure to initialize security policy data at startup may result in per-request policy checks being silently skipped.
What happened
The AWS API MCP Server, an open source tool enabling AI assistants to interact with AWS services, is under investigation for a potential security bypass. Reportedly, if the security policy data fails to initialize correctly at server startup, the per-request policy checks appear to be silently skipped for the duration of the process. This could potentially allow unauthorized actions to be executed without proper security validation.
Affected versions include aws-api-mcp-server (pypi) from >=0.2.13 to <1.3.47. It is recommended to upgrade to version 1.3.47 to mitigate this issue. Additionally, any forked or derivative code should be reviewed and patched accordingly. For more detailed information, consult the primary source at [GHSA-29w2-fq35-v728](https://github.com/awslabs/mcp/security/advisories/GHSA-29w2-fq35-v728).
Professionals using the AWS API MCP Server should assess their exposure by checking their current version against the affected range and applying the recommended upgrade. Further details on the nature and extent of the compromise should be obtained from the primary sources as the investigation continues.
How 0Day mitigates this
aws-api-mcp-server is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.