googleAds_enable_campaign
Enable a paused campaign
This record as markdown: /tools/io-github-alifanov-scopegate/googleads-enable-campaign.md
What googleAds_enable_campaign does on ScopeGate
AI agents use googleAds_enable_campaign 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_enable_campaign is rated Medium
Enabling a campaign modifies data (campaign state) reversibly—the campaign can be paused again. This is a Write operation, not Execute (no arbitrary code/command execution), not Destructive (fully reversible), and not Financial (though it may trigger ad spend, the tool itself only changes state; billing is a downstream consequence).
From the tool's definition Tool name 'googleAds_enable_campaign' and description 'Enable a paused campaign' indicate modification of campaign state.
Attacks that exploit this kind of access
The rule that runs googleAds_enable_campaign 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_enable_campaign, this is the rule to start with:
googleAds_enable_campaign 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_enable_campaign call is checked against it from then on.
Questions about googleAds_enable_campaign
Enable a paused campaign. 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_enable_campaign: 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_enable_campaign 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_enable_campaign 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_enable_campaign. 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_enable_campaign 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