Low Risk

google_ads_ads_list

Lists ads in a Google Ads account, optionally scoped to one

How to control google_ads_ads_list ↓

What google_ads_ads_list does on Mureo

AI agents call google_ads_ads_list to retrieve information from Mureo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why google_ads_ads_list needs a policy

This tool queries and retrieves ad data from a Google Ads account without modifying, deleting, or executing operations. However, severity is elevated from low to medium because: (1) it accesses advertising account data which may include business-sensitive information, campaign strategies, and performance insights; (2) unauthorized enumeration of ads could enable competitive intelligence gathering; (3) in the context…

From the tool's definition Tool name 'google_ads_ads_list' and description 'Lists ads in a Google Ads account' indicate a retrieval operation with no side effects. The verb 'list' is a classic Read operation.

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

How to control google_ads_ads_list

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_ads_list:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "google_ads_ads_list": {}
  }
}

google_ads_ads_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about google_ads_ads_list

What does the google_ads_ads_list tool do? +

Lists ads in a Google Ads account, optionally scoped to one. It is categorised as a Read tool in the Mureo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on google_ads_ads_list? +

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

google_ads_ads_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit google_ads_ads_list? +

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

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

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

Free to start. No card required.

185 Mureo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.