payments_custom_provider_marketplace_app_update_capabilities

Custom-provider marketplace app update capabilities

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Medium RISK CLASS

Category Write

Parameters 31 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/payments-custom-provider-marketplace-app-update-capabilities.md

WHAT IT DOES

What payments_custom_provider_marketplace_app_update_capabilities does on Ghl

AI agents use payments_custom_provider_marketplace_app_update_capabilities 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
`companyId`	string	—	Company id. Mandatory if locationId is not provided
`locationId`	string	—	Location / Sub-account id. Mandatory if companyId is not provided Defaults to GHL_LOCATION_ID when omitted.
`supportsSubscriptionSchedules`	boolean	Yes	Whether the marketplace app supports subscription schedules or not

Parameters from the server's own tool schema.

RISK

Why payments_custom_provider_marketplace_app_update_capabilities is rated Medium

An AI agent can call payments_custom_provider_marketplace_app_update_capabilities 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 payments_custom_provider_marketplace_app_update_capabilities 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 payments_custom_provider_marketplace_app_update_capabilities, this is the rule to start with:

payments_custom_provider_marketplace_app_update_capabilities Rate-limited

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

FAQ

Questions about payments_custom_provider_marketplace_app_update_capabilities

What does the payments_custom_provider_marketplace_app_update_capabilities tool do? +

Custom-provider marketplace app update capabilities. 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 payments_custom_provider_marketplace_app_update_capabilities accept? +

payments_custom_provider_marketplace_app_update_capabilities accepts 3 parameters: companyId, locationId, supportsSubscriptionSchedules. Required: supportsSubscriptionSchedules. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on payments_custom_provider_marketplace_app_update_capabilities? +

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

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

Can I rate-limit payments_custom_provider_marketplace_app_update_capabilities? +

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

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

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