funnels_update_redirect_by_id

Update Redirect By Id

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Medium RISK CLASS

Category Write

Parameters 43 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/funnels-update-redirect-by-id.md

WHAT IT DOES

What funnels_update_redirect_by_id does on Ghl

AI agents use funnels_update_redirect_by_id to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.

Parameter	Type	Required	Description
`id`	string	Yes
`action`	string	Yes
`target`	string	Yes
`locationId`	string	—	Defaults to GHL_LOCATION_ID when omitted.

Parameters from the server's own tool schema.

RISK

Why funnels_update_redirect_by_id is rated Medium

An AI agent can call funnels_update_redirect_by_id faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs funnels_update_redirect_by_id safely

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

funnels_update_redirect_by_id Rate-limited

funnels_update_redirect_by_id stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "funnels_update_redirect_by_id": {
      "limits": [
        {
          "counter": "funnels_update_redirect_by_id_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every funnels_update_redirect_by_id call is checked against it from then on.

FAQ

Questions about funnels_update_redirect_by_id

What does the funnels_update_redirect_by_id tool do? +

Update Redirect By Id. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does funnels_update_redirect_by_id accept? +

funnels_update_redirect_by_id accepts 4 parameters: id, action, target, locationId. Required: id, action, target. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on funnels_update_redirect_by_id? +

Register the Ghl MCP server in PolicyLayer and add a rule for funnels_update_redirect_by_id: 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 Ghl. Nothing to install.

What risk level is funnels_update_redirect_by_id? +

funnels_update_redirect_by_id is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit funnels_update_redirect_by_id? +

Yes. Add a rate_limit block to the funnels_update_redirect_by_id 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 funnels_update_redirect_by_id completely? +

Set action: deny in the PolicyLayer policy for funnels_update_redirect_by_id. 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 funnels_update_redirect_by_id? +

funnels_update_redirect_by_id is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 569 Ghl tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →