ad_manager_google_upsert_segment

Upsert segment

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Medium RISK CLASS

Category Write

Parameters 122 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/ad-manager-google-upsert-segment.md

WHAT IT DOES

What ad_manager_google_upsert_segment does on Ghl

AI agents use ad_manager_google_upsert_segment 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
`id`	string	—	Segment identifier
`name`	string	Yes	Segment name
`type`	string	Yes	Segment type
`status`	string	—	Segment status
`members`	array	—	Segment members — keywords, URLs, or apps that define the custom segment
`locationId`	string	—	Location identifier Defaults to GHL_LOCATION_ID when omitted.
`description`	string	—	Segment description
`countryCodes`	array	—	Country codes
`expansionLevel`	string	—	Expansion level
`seedUserListIds`	array	—	Seed user list IDs
`membershipStatus`	string	—	Membership status
`ruleBasedUserList`	object	—	Rule-based user list config

Parameters from the server's own tool schema.

RISK

Why ad_manager_google_upsert_segment is rated Medium

An AI agent can call ad_manager_google_upsert_segment 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.

Risk signalsHigh parameter count (15 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ad_manager_google_upsert_segment Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ad_manager_google_upsert_segment": {
      "limits": [
        {
          "counter": "ad_manager_google_upsert_segment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about ad_manager_google_upsert_segment

What does the ad_manager_google_upsert_segment tool do? +

Upsert segment. 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.

What parameters does ad_manager_google_upsert_segment accept? +

ad_manager_google_upsert_segment accepts 12 parameters: id, name, type, status, members, locationId, description, countryCodes, expansionLevel, seedUserListIds, membershipStatus, ruleBasedUserList. Required: name, type. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ad_manager_google_upsert_segment? +

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

ad_manager_google_upsert_segment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ad_manager_google_upsert_segment? +

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

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

ad_manager_google_upsert_segment 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

team_manager_emit_decision on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →