payments_fetch_config

Fetch given provider config

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/payments-fetch-config.md

WHAT IT DOES

What payments_fetch_config does on Ghl

AI agents call payments_fetch_config 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
`locationId`	string	—	Location id Defaults to GHL_LOCATION_ID when omitted.

Parameters from the server's own tool schema.

RISK

Why payments_fetch_config is rated Low

Even though payments_fetch_config 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

RECOMMENDED RULE

The rule that runs payments_fetch_config 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 payments_fetch_config, this is the rule to start with:

payments_fetch_config Allowed

payments_fetch_config is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every payments_fetch_config call is checked against it from then on.

FAQ

Questions about payments_fetch_config

What does the payments_fetch_config tool do? +

Fetch given provider config. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.

What parameters does payments_fetch_config accept? +

payments_fetch_config accepts 1 parameter: locationId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on payments_fetch_config? +

Register the Ghl MCP server in PolicyLayer and add a rule for payments_fetch_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 Ghl. Nothing to install.

What risk level is payments_fetch_config? +

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

Can I rate-limit payments_fetch_config? +

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

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

payments_fetch_config 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.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 569 Ghl tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →