google_ads_campaigns_update_status

Sets the delivery status of a single campaign to ENABLED,

SERVERMureo SOURCElogly/mureo

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/logly-mureo/google-ads-campaigns-update-status.md

WHAT IT DOES

What google_ads_campaigns_update_status does on Mureo

AI agents use google_ads_campaigns_update_status to create or update resources in Mureo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mureo environment.

RISK

Why google_ads_campaigns_update_status is rated Medium

This tool modifies the operational state of an advertising campaign, enabling or disabling its delivery. While reversible (status can be toggled back), changing campaign delivery status has immediate financial and operational impact: it directly affects ad spend, impressions, and campaign performance.

From the tool's definition Tool name includes 'update' and description states 'Sets the delivery status' — modifies campaign state. Description appears incomplete ('ENABLED,' with trailing comma suggests truncation), but the core function is clearly state modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs google_ads_campaigns_update_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mureo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For google_ads_campaigns_update_status, this is the rule to start with:

google_ads_campaigns_update_status Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "google_ads_campaigns_update_status": {
      "limits": [
        {
          "counter": "google_ads_campaigns_update_status_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 Mureo, apply this rule, and every google_ads_campaigns_update_status call is checked against it from then on.

FAQ

Questions about google_ads_campaigns_update_status

What does the google_ads_campaigns_update_status tool do? +

Sets the delivery status of a single campaign to ENABLED,. It is categorised as a Write tool in the Mureo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on google_ads_campaigns_update_status? +

Register the Mureo MCP server in PolicyLayer and add a rule for google_ads_campaigns_update_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 Mureo. Nothing to install.

What risk level is google_ads_campaigns_update_status? +

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

Can I rate-limit google_ads_campaigns_update_status? +

Yes. Add a rate_limit block to the google_ads_campaigns_update_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.

How do I block google_ads_campaigns_update_status completely? +

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

What MCP server provides google_ads_campaigns_update_status? +

google_ads_campaigns_update_status is provided by the Mureo MCP server (logly/mureo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mureo, and thousands of servers like it.

This server

All 225 Mureo tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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