get_custom_provider_config

Fetch existing payment config for a location

SERVERGoHighLevel MCP Server SOURCEhooker-dev/hailey-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hooker-dev-hailey-mcp/get-custom-provider-config.md

What get_custom_provider_config does on GoHighLevel MCP Server

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.

Why get_custom_provider_config is rated Low

This tool retrieves payment configuration data (a Read operation). However, it accesses sensitive financial configuration details that could expose payment processing credentials or API keys if returned in plaintext, elevating severity from low to medium. The tool performs no write, execute, or destructive actions—it only queries existing configuration.

From the tool's definition Tool name 'get_custom_provider_config' and description 'Fetch existing payment config for a location' indicate data retrieval without modification.

Questions about get_custom_provider_config

What does the get_custom_provider_config tool do? +

Fetch existing payment config for a location. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_custom_provider_config? +

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

What risk level is get_custom_provider_config? +

get_custom_provider_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_custom_provider_config? +

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

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

get_custom_provider_config is provided by the GoHighLevel MCP Server MCP server (hooker-dev/hailey-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on GoHighLevel MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GoHighLevel MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.