google_ads_keywords_cross_adgroup_duplicates
Finds the same text+match_type keyword appearing across
This record as markdown: /tools/logly-mureo/google-ads-keywords-cross-adgroup-duplicates.md
What google_ads_keywords_cross_adgroup_duplicates does on Mureo
AI agents call google_ads_keywords_cross_adgroup_duplicates 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.
Why google_ads_keywords_cross_adgroup_duplicates is rated Low
This tool queries Google Ads data to identify duplicate keywords across ad groups. It performs no creation, modification, deletion, or execution of external operations. It is a read-only analysis tool with minimal blast radius if misused by an AI agent — an attacker could only discover keyword duplicates, not alter accounts or spending.
From the tool's definition Tool name indicates 'Finds' and 'cross_adgroup_duplicates' — a detection/query operation. Description fragment 'Finds the same text+match_type keyword appearing across' confirms it searches for and retrieves keyword data without modification.
Attacks that exploit this kind of access
The rule that runs google_ads_keywords_cross_adgroup_duplicates 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_keywords_cross_adgroup_duplicates, this is the rule to start with:
google_ads_keywords_cross_adgroup_duplicates is read-only, so it stays allowed. 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_keywords_cross_adgroup_duplicates call is checked against it from then on.
Questions about google_ads_keywords_cross_adgroup_duplicates
Finds the same text+match_type keyword appearing across. It is categorised as a Read tool in the Mureo MCP Server, which means it retrieves data without modifying state.
Register the Mureo MCP server in PolicyLayer and add a rule for google_ads_keywords_cross_adgroup_duplicates: 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_keywords_cross_adgroup_duplicates is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the google_ads_keywords_cross_adgroup_duplicates 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_keywords_cross_adgroup_duplicates. 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_keywords_cross_adgroup_duplicates 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