Public IP whitelist for Custom MCP connections
C
Chris Wanzung
I want to host MCP tools in Azure Functions and restrict inbound traffic to only Hatz’s outbound IPs. Today there is a list of domains you can whitelist for Hatz AI, but not an official public IP whitelist containing the IPs Hatz uses for its outbound connections. Specifically, it would be nice to have this for the MCP connections.
C
Chris Trompeter
Really need this for security of these tools
B
Brent Wagner
Our internal n8n server has API access to all our most sensitive tools. We can't use the n8n integration with Hatz until we can restrict the inbound source traffic to a narrow range of IPs.
We've observed in logs that Hatz uses a variety of Google Cloud IPs to initiate the connection. Documentation indicates that for Connectwise, there is a single IP that can be whitelisted, but according to the support chat agent, that is the only one that has such a constraint. This needs to be extended to other integrations.
B
Brent Wagner
Our internal n8n server has API access to all our most sensitive tools. We can't use the n8n integration with Hatz until we can restrict the inbound source traffic to a narrow range of IPs.
We've observed in logs that Hatz uses a variety of Google Cloud IPs to initiate the connection. Documentation indicates that for Connectwise, there is a single IP that can be whitelisted, but according to the support chat agent, that is the only one that has such a constraint. This needs to be extended to other integrations.