New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

google_ads_ads_create_display

Creates a Responsive Display Ad (RDA) in a DISPLAY campaign

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-ads-create-display.md

What google_ads_ads_create_display does on Mureo

AI agents use google_ads_ads_create_display 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_display is rated Medium

This tool creates new ad assets within Google Ads campaigns, which is a reversible write operation. It does not delete data (not Destructive), does not move money directly (not Financial—though ad creation can trigger spend, the tool itself only creates the ad structure), and does not execute arbitrary code (not Execute).

From the tool's definition Tool name explicitly contains 'create' and description states 'Creates a Responsive Display Ad (RDA) in a DISPLAY campaign'. This is a data creation operation that modifies advertising accounts.

Questions about google_ads_ads_create_display

What does the google_ads_ads_create_display tool do? +

Creates a Responsive Display Ad (RDA) in a DISPLAY campaign. 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_ads_create_display? +

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

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

Can I rate-limit google_ads_ads_create_display? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mureo's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.