saas_api_pause_location

Pause location (requires an agency-level token, not a location PIT)

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Low RISK CLASS

Category Read

Parameters 32 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/saas-api-pause-location.md

WHAT IT DOES

What saas_api_pause_location does on Ghl

AI agents call saas_api_pause_location 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
`paused`	boolean	Yes	Paused
`companyId`	string	Yes	Company ID
`locationId`	string	—	Defaults to GHL_LOCATION_ID when omitted.

Parameters from the server's own tool schema.

RISK

Why saas_api_pause_location is rated Low

Even though saas_api_pause_location 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 saas_api_pause_location 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 saas_api_pause_location, this is the rule to start with:

saas_api_pause_location Allowed

saas_api_pause_location 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": {
    "saas_api_pause_location": {}
  }
}

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 saas_api_pause_location call is checked against it from then on.

FAQ

Questions about saas_api_pause_location

What does the saas_api_pause_location tool do? +

Pause location (requires an agency-level token, not a location PIT). It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.

What parameters does saas_api_pause_location accept? +

saas_api_pause_location accepts 3 parameters: paused, companyId, locationId. Required: paused, companyId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on saas_api_pause_location? +

Register the Ghl MCP server in PolicyLayer and add a rule for saas_api_pause_location: 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 saas_api_pause_location? +

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

Can I rate-limit saas_api_pause_location? +

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

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

saas_api_pause_location 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 →