debug_config

What debug_config does on GoHighLevel MCP Server

AI agents call debug_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 debug_config is rated Low

This tool only reads and displays diagnostic information about the server state. It has no side effects, does not execute arbitrary code, and does not modify or delete data. The blast radius of misuse is minimal—an attacker would only gain visibility into configuration details, which while sensitive, does not grant direct access to CRM operations or data modification. Classified as Read with low severity.

From the tool's definition Tool description states it is a 'Debug tool to show current MCP server configuration and auth status' — it retrieves and displays configuration and authentication metadata without modifying, executing, or deleting anything.

The rule that runs debug_config safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For debug_config, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "debug_config": {}
  }
}

Questions about debug_config