google_ads_schedule_targeting_update

THE RISK

Medium Risk

Why google_ads_schedule_targeting_update needs a policy

This tool modifies advertising configuration (schedule targeting) within a Google Ads account. While reversible and thus not destructive, it represents a write operation with high severity because: (1) it directly alters active ad campaigns' behavior, affecting ad delivery and spend; (2) unintended changes could cause ads to run at wrong times, wasting budget; (3) the blast radius includes financial impact (altered…

From the tool's definition The tool performs an update operation on ad-schedule criteria in Google Ads: 'Add and/or remove ad-schedule criteria on a Google Ads'. The verbs 'add' and 'remove' indicate creation and modification of targeting criteria, which are reversible data changes.

Documented attack patterns abuse exactly the kind of access google_ads_schedule_targeting_update gives an agent:

POLICY

How to control google_ads_schedule_targeting_update

PolicyLayer is an MCP gateway — it sits between your AI agents and Mureo, and nothing reaches the server without passing your rules. This is the rule we recommend for google_ads_schedule_targeting_update:

policy.json

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

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

Create a free account and register Mureo — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Mureo tools

Financial google_ads_budget_reallocation Propose a budget reallocation plan by cutting up to 20% Financial meta_ads_instagram_boost Boosts an organic Instagram post by creating a paid ad Financial meta_ads_page_posts_boost Boosts an existing Facebook Page post by creating a paid Destructive google_ads_callouts_remove Detach a callout asset from a Google Ads campaign by Destructive google_ads_conversions_remove Archive (status=REMOVED) a Google Ads conversion action. Destructive google_ads_keywords_remove Removes (soft-deletes) a single keyword criterion from an ad Destructive google_ads_negative_keywords_remove Removes a single campaign-level negative keyword. Returns the Destructive google_ads_sitelinks_remove Detach a sitelink asset from a Google Ads campaign by

All 185 Mureo tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about google_ads_schedule_targeting_update

What does the google_ads_schedule_targeting_update tool do? +

Add and/or remove ad-schedule criteria on a Google Ads. 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_schedule_targeting_update? +

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

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

Can I rate-limit google_ads_schedule_targeting_update? +

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

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

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

Enforce policy on every Mureo tool call.

Start from Mureo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →