# get_custom_provider_config

Fetch existing payment config for a location

Agent View of the PolicyLayer registry record for `get_custom_provider_config`. HTML page: https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/get-custom-provider-config

## Facts

- Tool: `get_custom_provider_config`
- Server: GoHighLevel MCP Server (`busybee3333/go-high-level-mcp-2026-complete`) — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete.md
- Homepage: https://github.com/BusyBee3333/Go-High-Level-MCP-2026-Complete
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_custom_provider_config",
    "arguments": {}
  }
}
```

## Why get_custom_provider_config is rated Low

This tool retrieves payment configuration details for a location. While it is a Read operation (no data modification), the sensitivity of payment configuration data—which may include API keys, merchant credentials, or gateway settings—elevates the severity to medium. Unauthorized access to such configuration could enable payment fraud or system compromise, even without direct write/execute capability.

From the tool's own definition: "Tool name 'get_custom_provider_config' and description 'Fetch existing payment config for a location' indicate retrieval of configuration data. The verb 'Fetch' and lack of modification language confirm this is a read operation."

## Use case

AI agents call get_custom_provider_config 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches GoHighLevel MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_custom_provider_config": {}
  }
}
```

## Other tools on GoHighLevel MCP Server (565)

- `bulk_delete_social_posts` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/bulk-delete-social-posts.md
- `cancel_scheduled_campaign_message` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/cancel-scheduled-campaign-message.md
- `cancel_scheduled_email` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/cancel-scheduled-email.md
- `cancel_scheduled_message` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/cancel-scheduled-message.md
- `delete_affiliate` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-affiliate.md
- `delete_affiliate_campaign` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-affiliate-campaign.md
- `delete_api_key` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-api-key.md
- `delete_appointment` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-appointment.md
- `delete_appointment_note` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-appointment-note.md
- `delete_business` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-business.md
- `delete_calendar` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-calendar.md
- `delete_calendar_group` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-calendar-group.md
- `delete_calendar_notification` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-calendar-notification.md
- `delete_calendar_resource_equipment` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-calendar-resource-equipment.md
- `delete_calendar_resource_room` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-calendar-resource-room.md
- `delete_caller_id` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-caller-id.md
- `delete_campaign` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-campaign.md
- `delete_company` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-company.md
- `delete_contact` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-contact.md
- `delete_contact_note` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-contact-note.md
- `delete_contact_task` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-contact-task.md
- `delete_conversation` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-conversation.md
- `delete_coupon` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-coupon.md
- `delete_course` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-course.md
- `delete_course_category` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-course-category.md
- `delete_course_offer` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-course-offer.md
- `delete_course_post` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-course-post.md
- `delete_course_product` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-course-product.md
- `delete_custom_menu` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-custom-menu.md
- `delete_custom_provider_integration` — Destructive — https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete/delete-custom-provider-integration.md
- …and 535 more: https://policylayer.com/tools/busybee3333-go-high-level-mcp-2026-complete.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=busybee3333-go-high-level-mcp-2026-complete · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/busybee3333-go-high-level-mcp-2026-complete