debug_config

THE RISK

Low Risk

Why debug_config needs a policy

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.

Documented attack patterns abuse exactly the kind of access debug_config gives an agent:

POLICY

How to control debug_config

PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for debug_config:

policy.json

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

debug_config is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register GoHighLevel MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GoHighLevel MCP Server tools

Destructive delete_appointment Delete an appointment Destructive delete_contact Delete a contact from GoHighLevel Destructive delete_contact_note Delete a note from a contact Destructive delete_contact_task Delete a task from a contact Destructive delete_custom_field Delete a custom field Destructive delete_custom_value Delete a custom value Destructive delete_opportunity Delete an opportunity from GoHighLevel Destructive delete_user Delete a user

All 64 GoHighLevel MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

Roll out MCP under one policy → Per-person scoped tokens, one central policy, and full audit across every server your team connects.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about debug_config

What does the debug_config tool do? +

Debug tool to show current MCP server configuration and auth status. 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 debug_config? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for debug_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 debug_config? +

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

Can I rate-limit debug_config? +

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

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

debug_config is provided by the GoHighLevel MCP Server MCP server (basicmachines-co/open-ghl-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GoHighLevel MCP Server tool call.

Start from GoHighLevel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →