google_ads_ads_list

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

SERVERMureo SOURCElogly/mureo

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/logly-mureo/google-ads-ads-list.md

WHAT IT DOES

What google_ads_ads_list does on Mureo

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

RISK

Why google_ads_ads_list is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs google_ads_ads_list 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_list, this is the rule to start with:

google_ads_ads_list Allowed

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "google_ads_ads_list": {}
  }
}

ALLOW ONLY 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_ads_list call is checked against it from then on.

FAQ

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.

KEEP EXPLORING

More on Mureo, and thousands of servers like it.

This server

All 225 Mureo tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →