fetch-redirects-list

Retrieves a list of all URL redirects based on the given query parameters.

SERVERGoHighLevel MCP Server SOURCEdrausal/gohighlevel-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/drausal-gohighlevel-mcp/fetch-redirects-list.md

WHAT IT DOES

What fetch-redirects-list does on GoHighLevel MCP Server

AI agents call fetch-redirects-list to retrieve information from GoHighLevel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why fetch-redirects-list is rated Low

This tool fetches and lists existing redirect data without modifying, deleting, or executing any operations. It is a pure read operation that retrieves information based on query parameters. The blast radius of misuse is minimal—an agent could only retrieve redirect information that may already be accessible through other means.

From the tool's definition Tool name 'fetch-redirects-list' and description 'Retrieves a list of all URL redirects' indicates a query/retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fetch-redirects-list safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fetch-redirects-list, this is the rule to start with:

fetch-redirects-list Allowed

fetch-redirects-list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fetch-redirects-list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GoHighLevel MCP Server, apply this rule, and every fetch-redirects-list call is checked against it from then on.

FAQ

Questions about fetch-redirects-list

What does the fetch-redirects-list tool do? +

Retrieves a list of all URL redirects based on the given query parameters. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch-redirects-list? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for fetch-redirects-list: 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 GoHighLevel MCP Server. Nothing to install.

What risk level is fetch-redirects-list? +

fetch-redirects-list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fetch-redirects-list? +

Yes. Add a rate_limit block to the fetch-redirects-list 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.

How do I block fetch-redirects-list completely? +

Set action: deny in the PolicyLayer policy for fetch-redirects-list. 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.

What MCP server provides fetch-redirects-list? +

fetch-redirects-list is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GoHighLevel MCP Server, and thousands of servers like it.

This server

All 406 GoHighLevel MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →