This record as markdown: /tools/aiwerk-mcp-server-ghl/marketplace-get-charges.md
What marketplace_get_charges does on Ghl
AI agents call marketplace_get_charges to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
skip | number | — | Number of records to skip |
limit | number | — | Maximum number of records to return |
userId | string | — | Filter results by User ID that your server passed via API when the charge was created |
endDate | string | — | Filter results BEFORE a specific date. Use this in combination with startDate to filter results in a specific time window. |
eventId | string | — | Event ID / Transaction ID |
meterId | string | — | Billing Meter ID (you can find this on your app's pricing page on the developer portal) |
startDate | string | — | Filter results AFTER a specific date. Use this in combination with endDate to filter results in a specific time window. |
Parameters from the server's own tool schema.
Why marketplace_get_charges is rated Low
Even though marketplace_get_charges only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs marketplace_get_charges safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For marketplace_get_charges, this is the rule to start with:
marketplace_get_charges 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 Ghl, apply this rule, and every marketplace_get_charges call is checked against it from then on.
Questions about marketplace_get_charges
Get all wallet charges. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
marketplace_get_charges accepts 7 parameters: skip, limit, userId, endDate, eventId, meterId, startDate. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for marketplace_get_charges: 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 Ghl. Nothing to install.
marketplace_get_charges 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 marketplace_get_charges 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 marketplace_get_charges. 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.
marketplace_get_charges is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue