marketplace_migrate_connection

Migrate external authentication connection

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Medium RISK CLASS

Category Write

Parameters 124 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/marketplace-migrate-connection.md

WHAT IT DOES

What marketplace_migrate_connection does on Ghl

AI agents use marketplace_migrate_connection 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
`type`	string	Yes	Type of authentication - basic or oauth2
`appId`	string	Yes	App ID
`apiKey`	string	—	API Key (supported when type is basic)
`scopes`	array	—	OAuth2 scopes (optional for oauth2)
`expiryAt`	number	—	Timestamp for access token expiry (optional for oauth2)
`expiryIn`	number	—	Access token expiry time in milliseconds (optional for oauth2)
`accountId`	string	Yes	Connection identifier
`isDefault`	boolean	—	Whether this is the default connection for the location (optional, defaults to false)
`locationId`	string	—	Location ID Defaults to GHL_LOCATION_ID when omitted.
`accessToken`	string	—	Access token (required when type is oauth2)
`displayName`	string	—	Display name for the connection (optional, defaults to accountId)
`appVersionId`	string	Yes	App Version ID

Parameters from the server's own tool schema.

RISK

Why marketplace_migrate_connection is rated Medium

An AI agent can call marketplace_migrate_connection 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.

Risk signalsHandles credentials or secrets (apiKey) · High parameter count (14 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs marketplace_migrate_connection 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 marketplace_migrate_connection, this is the rule to start with:

marketplace_migrate_connection Rate-limited

marketplace_migrate_connection 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": {
    "marketplace_migrate_connection": {
      "limits": [
        {
          "counter": "marketplace_migrate_connection_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 marketplace_migrate_connection call is checked against it from then on.

FAQ

Questions about marketplace_migrate_connection

What does the marketplace_migrate_connection tool do? +

Migrate external authentication connection. 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 marketplace_migrate_connection accept? +

marketplace_migrate_connection accepts 12 parameters: type, appId, apiKey, scopes, expiryAt, expiryIn, accountId, isDefault, locationId, accessToken, displayName, appVersionId. Required: type, appId, accountId, appVersionId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on marketplace_migrate_connection? +

Register the Ghl MCP server in PolicyLayer and add a rule for marketplace_migrate_connection: 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 marketplace_migrate_connection? +

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

Can I rate-limit marketplace_migrate_connection? +

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

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

marketplace_migrate_connection 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

The MCP Attack Database →

Guides

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