google_ads_ads_create
Creates a Responsive Search Ad (RSA) in the specified ad
This record as markdown: /tools/logly-mureo/google-ads-ads-create.md
What google_ads_ads_create does on Mureo
AI agents use google_ads_ads_create 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.
Why google_ads_ads_create is rated Medium
This tool creates new advertising content within Google Ads, which modifies the customer's ad account state by adding a new ad resource. While creations are Write-category actions, the severity is high because an AI agent operating this autonomously without guardrails could create ineffective, policy-violating, or brand-damaging ads at scale, or exhaust budget on unwanted ad variants.
From the tool's definition Creates a Responsive Search Ad (RSA) in the specified ad group — the verb 'Creates' and action of instantiating a new ad demonstrates data creation. This is reversible (ads can be paused/deleted), not irreversible destruction.
Attacks that exploit this kind of access
The rule that runs google_ads_ads_create 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_ads_create, this is the rule to start with:
google_ads_ads_create 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 Mureo, apply this rule, and every google_ads_ads_create call is checked against it from then on.
Questions about google_ads_ads_create
Creates a Responsive Search Ad (RSA) in the specified ad. 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.
Register the Mureo MCP server in PolicyLayer and add a rule for google_ads_ads_create: 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.
google_ads_ads_create 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_ads_create 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_ads_create. 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_ads_create 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.
More on Mureo, and thousands of servers like it.
This server
Across the catalogue