Rank ENABLED ads within a single Google Ads ad group and
AI agents call google_ads_ad_performance_compare 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.
The tool compares and ranks ad performance data within an ad group, which is a read/query operation with no side effects. It retrieves metrics and ranks them without modifying any data. The description appears truncated but the core action is analytical ranking of existing ads. Severity is low as misuse only exposes performance data.
From the tool's definition "Rank ENABLED ads within a single Google Ads ad group" — this is a read/analysis operation that retrieves and ranks performance data
Documented attack patterns abuse exactly the kind of access google_ads_ad_performance_compare gives an agent:
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_ad_performance_compare:
{
"version": "1",
"default": "deny",
"tools": {
"google_ads_ad_performance_compare": {}
}
} google_ads_ad_performance_compare is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Rank ENABLED ads within a single Google Ads ad group and. 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_ad_performance_compare: 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_ad_performance_compare 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_ad_performance_compare 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_ad_performance_compare. 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_ad_performance_compare 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.
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.