getSpecificCharge
Get specific wallet charge details
This record as markdown: /tools/drausal-gohighlevel-mcp/getspecificcharge.md
What getSpecificCharge does on GoHighLevel MCP Server
AI agents call getSpecificCharge 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 getSpecificCharge is rated Low
This tool retrieves or queries information about a specific charge from a wallet—a read-only operation with no side effects. It does not create, modify, delete, or process payments; it merely fetches existing charge details. The low severity reflects minimal blast radius even if misused by an agent, as it only exposes financial history/data rather than enabling transactions or destructive actions.
From the tool's definition Tool name 'getSpecificCharge' and description 'Get specific wallet charge details' indicate retrieval of existing financial data with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs getSpecificCharge 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 getSpecificCharge, this is the rule to start with:
getSpecificCharge is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GoHighLevel MCP Server, apply this rule, and every getSpecificCharge call is checked against it from then on.
Questions about getSpecificCharge
Get specific wallet charge details. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for getSpecificCharge: 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.
getSpecificCharge is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getSpecificCharge 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.
Set action: deny in the PolicyLayer policy for getSpecificCharge. 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.
getSpecificCharge is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-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.
This server
Across the catalogue