Repository navigation
This release contains a security fix. All deployments should update.
Security fix
- Tool calls no longer follow HTTP redirects returned by tool pods. Previously, the tool gateway and agent runs sent tool invocations with an HTTP client that followed redirects, so a tool pod could redirect the gateway to another host it can reach and have that host's response returned as the tool result. A redirect from a tool pod is now returned as a tool error, and the redirect target is never requested. (#117)
No configuration changes are required.
Upgrading
The fix is in both the gateway and the tool gateway images, tagged 1.0.1:
| Image | Digest |
|---|---|
ghcr.io/microsoft/mcp-gateway:1.0.1 |
sha256:5a01433b8a3036ce961ebf2232f64460783b054962c8d167cb3d41c4452738f9 |
ghcr.io/microsoft/tool-gateway:1.0.1 |
sha256:f1e4860e4c859267c3012bb25538dc2a5281d3821a8fc692ff7026a244649e6c |
To pin this release, set both images to the 1.0.1 tags (for the Azure template, the gatewayImage and toolGatewayImage parameters) and redeploy. If your deployment uses the latest images, restart both workloads so they pull the fixed images:
kubectl rollout restart deployment/mcpgateway statefulset/toolgateway -n <namespace>
If you build your own images, rebuild them from v1.0.1 and redeploy.
Other changes
- Dependency updates for the management portal (vite), the MCP proxy sample (fastmcp), and GitHub Actions (#111, #113, #114, #115, #116)
Full Changelog: v1.0.0...v1.0.1