mcp-proxy-for-aws

The project leverages standard AWS SDKs (boto3, botocore) for secure SigV4 authentication, reducing common credential-handling risks. It includes a `ToolFilteringMiddleware` to disable tools requiring write permissions, enhancing security. Input validation is performed for CLI arguments. A monkey patch to `fastmcp` exists to fix a specific error propagation issue, which is a controlled modification for protocol correctness. No direct `eval` or `exec` usage was found. Potential network risks could arise if configured with an untrusted upstream MCP endpoint that exploits `httpx`'s default `follow_redirects` or sends excessively large/malformed error responses, though these are standard HTTP client behaviors. Overall, security is well-considered, but proper AWS IAM configuration and trusted upstream services are critical.