saas_api_enable_saas_location_deprecated

Enable SaaS for Sub-Account (Formerly Location) (requires an agency-level token, not a location PIT)

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Medium RISK CLASS

Category Write

Parameters 122 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/saas-api-enable-saas-location-deprecated.md

WHAT IT DOES

What saas_api_enable_saas_location_deprecated does on Ghl

AI agents use saas_api_enable_saas_location_deprecated 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
`name`	string	—	Name of the stripe customer(Required only for SaaS V1)
`email`	string	—	Email of the stripe customer(Required only for SaaS V1)
`priceId`	string	—	Required only while pre-configuring saas subscription
`isSaaSV2`	boolean	Yes	Denotes if it is a saas v2 or v1 sub-account
`companyId`	string	Yes
`contactId`	string	—	Agency subaccount used for payment provider integration(Required Only for SaaS V2)
`locationId`	string	—	Location ID to enable SaaS for Defaults to GHL_LOCATION_ID when omitted.
`saasPlanId`	string	—	Required only while pre-configuring saas subscription
`description`	string	—	Description
`stripeAccountId`	string	—	Stripe account id(Required only for SaaS V1)
`stripeCustomerId`	string	—	Stripe customer id if exists(Required only for SaaS V1)
`providerLocationId`	string	—	Agency Subaccount ID

Parameters from the server's own tool schema.

RISK

Why saas_api_enable_saas_location_deprecated is rated Medium

An AI agent can call saas_api_enable_saas_location_deprecated 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 signalsHigh parameter count (12 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

saas_api_enable_saas_location_deprecated Rate-limited

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

FAQ

Questions about saas_api_enable_saas_location_deprecated

What does the saas_api_enable_saas_location_deprecated tool do? +

Enable SaaS for Sub-Account (Formerly Location) (requires an agency-level token, not a location PIT). 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 saas_api_enable_saas_location_deprecated accept? +

saas_api_enable_saas_location_deprecated accepts 12 parameters: name, email, priceId, isSaaSV2, companyId, contactId, locationId, saasPlanId, description, stripeAccountId, stripeCustomerId, providerLocationId. Required: isSaaSV2, companyId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on saas_api_enable_saas_location_deprecated? +

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

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

Can I rate-limit saas_api_enable_saas_location_deprecated? +

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

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

saas_api_enable_saas_location_deprecated 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 →