http_redirect_chain
Follow an HTTP/HTTPS URL through all redirects and return every hop with status code and Location header. Useful for debugging redirect loops or verifying HTTPS redirect configuration.
This record as markdown: /tools/aaronckj-mcp-nettools/http-redirect-chain.md
What http_redirect_chain does on Mcp Nettools
AI agents call http_redirect_chain to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why http_redirect_chain is rated Low
This tool performs read-only network diagnostics by following HTTP redirects and collecting response metadata. It has no side effects on the target systems or data—it only observes and reports HTTP redirect chains. This is consistent with the network diagnostics purpose of the mcp-nettools server (ping, DNS lookup, traceroute, etc.).
From the tool's definition Tool follows HTTP/HTTPS URL redirects and returns status codes and Location headers. The description explicitly states it is for 'debugging redirect loops or verifying HTTPS redirect configuration' with no mention of modifying, deleting, or executing code.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs http_redirect_chain safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For http_redirect_chain, this is the rule to start with:
http_redirect_chain is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every http_redirect_chain call is checked against it from then on.
Questions about http_redirect_chain
Follow an HTTP/HTTPS URL through all redirects and return every hop with status code and Location header. Useful for debugging redirect loops or verifying HTTPS redirect configuration. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.
Register the Mcp Nettools MCP server in PolicyLayer and add a rule for http_redirect_chain: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mcp Nettools. Nothing to install.
http_redirect_chain is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the http_redirect_chain rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for http_redirect_chain. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
http_redirect_chain is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Nettools, and thousands of servers like it.
This server
Across the catalogue