This record as markdown: /tools/com-geekflare-mcp/redirectcheck.md
What redirectCheck does on Mcp
AI agents call redirectCheck to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Target URL |
proxyCountry | string | — | Country code for proxy routing |
Parameters from the server's own tool schema.
Why redirectCheck is rated Low
This tool performs a read-only query of URL redirect behavior. It gathers information about how a URL redirects without side effects, making it a Read category tool. The severity is low because misuse (e.g., checking many redirects) has minimal blast radius—it may consume resources but cannot alter systems or data.
From the tool's definition The tool 'redirectCheck' is described as checking 'the redirect chain of a URL' — it retrieves and inspects HTTP redirect information without modifying, deleting, or executing code. This is a passive inspection operation.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs redirectCheck safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For redirectCheck, this is the rule to start with:
redirectCheck 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, apply this rule, and every redirectCheck call is checked against it from then on.
Questions about redirectCheck
Check the redirect chain of a URL. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
redirectCheck accepts 2 parameters: url, proxyCountry. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for redirectCheck: 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. Nothing to install.
redirectCheck 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 redirectCheck 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 redirectCheck. 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.
redirectCheck is provided by the MCP server (@geekflare/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue