google_ads_update_campaign_status
A write tool on the All MCP server.
This record as markdown: /tools/allmcp/google-ads-update-campaign-status.md
What google_ads_update_campaign_status does on Allmcp
AI agents use google_ads_update_campaign_status to create or update resources in Allmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Allmcp environment.
Why google_ads_update_campaign_status is rated Medium
The tool updates campaign status, which is a reversible modification of existing data. This is a Write operation rather than Read (no query), Execute (no arbitrary code/external trigger), or Destructive (status changes are reversible). Severity is high because misconfigured campaign status changes could disable active advertising campaigns, causing immediate business impact and revenue loss.
From the tool's definition Tool name 'google_ads_update_campaign_status' indicates it modifies campaign status in Google Ads. The description is empty, limiting direct evidence, but the verb 'update' and the domain (advertising campaigns) clearly indicate state modification rather than…
Attacks that exploit this kind of access
The rule that runs google_ads_update_campaign_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Allmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For google_ads_update_campaign_status, this is the rule to start with:
google_ads_update_campaign_status 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 Allmcp, apply this rule, and every google_ads_update_campaign_status call is checked against it from then on.
Questions about google_ads_update_campaign_status
google_ads_update_campaign_status is a write tool on the All MCP server. It is categorised as a Write tool in the Allmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the All MCP server in PolicyLayer and add a rule for google_ads_update_campaign_status: 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 Allmcp. Nothing to install.
google_ads_update_campaign_status 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 google_ads_update_campaign_status 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 google_ads_update_campaign_status. 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.
google_ads_update_campaign_status is provided by the All MCP server (Perception-Dynamics-Inc/allmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on All, and thousands of servers like it.
This server
Across the catalogue