ad_manager_google_create_offline_user_list_job
Create offline user list job
This record as markdown: /tools/aiwerk-mcp-server-ghl/ad-manager-google-create-offline-user-list-job.md
What ad_manager_google_create_offline_user_list_job does on Ghl
AI agents use ad_manager_google_create_offline_user_list_job to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
csvPath | string | — | CSV file path |
isDynamic | boolean | — | Dynamic list flag |
locationId | string | — | Location identifier Defaults to GHL_LOCATION_ID when omitted. |
userListId | string | — | User list identifier |
smartListIds | array | — | Smart list IDs |
Parameters from the server's own tool schema.
Why ad_manager_google_create_offline_user_list_job is rated Medium
An AI agent can call ad_manager_google_create_offline_user_list_job faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs ad_manager_google_create_offline_user_list_job 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 ad_manager_google_create_offline_user_list_job, this is the rule to start with:
ad_manager_google_create_offline_user_list_job stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 ad_manager_google_create_offline_user_list_job call is checked against it from then on.
Questions about ad_manager_google_create_offline_user_list_job
Create offline user list job. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
ad_manager_google_create_offline_user_list_job accepts 5 parameters: csvPath, isDynamic, locationId, userListId, smartListIds. 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 ad_manager_google_create_offline_user_list_job: 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.
ad_manager_google_create_offline_user_list_job is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ad_manager_google_create_offline_user_list_job 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 ad_manager_google_create_offline_user_list_job. 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.
ad_manager_google_create_offline_user_list_job 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