googleAds_assign_label
Assign a label to a campaign, ad group, or ad
This record as markdown: /tools/io-github-alifanov-scopegate/googleads-assign-label.md
What googleAds_assign_label does on ScopeGate
AI agents use googleAds_assign_label to create or update resources in ScopeGate, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScopeGate environment.
Why googleAds_assign_label is rated Medium
Assigning labels is a write operation that modifies campaign/ad data but is reversible and does not delete, execute code, or move funds. The severity is medium because misuse could disrupt advertising operations or cause financial impact through campaign misconfiguration, but the operation itself is not destructive or financial in nature.
From the tool's definition Tool description states 'Assign a label to a campaign, ad group, or ad' — this modifies metadata/labels on advertising objects, which is a reversible change operation.
Attacks that exploit this kind of access
The rule that runs googleAds_assign_label safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For googleAds_assign_label, this is the rule to start with:
googleAds_assign_label 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 ScopeGate, apply this rule, and every googleAds_assign_label call is checked against it from then on.
Questions about googleAds_assign_label
Assign a label to a campaign, ad group, or ad. It is categorised as a Write tool in the ScopeGate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ScopeGate MCP server in PolicyLayer and add a rule for googleAds_assign_label: 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 ScopeGate. Nothing to install.
googleAds_assign_label 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 googleAds_assign_label 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 googleAds_assign_label. 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.
googleAds_assign_label is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue