google_ads_campaigns_diagnose
Explains why a campaign is not serving or is under-delivering.
This record as markdown: /tools/logly-mureo/google-ads-campaigns-diagnose.md
What google_ads_campaigns_diagnose does on Mureo
AI agents call google_ads_campaigns_diagnose 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_campaigns_diagnose is rated Low
This tool retrieves and analyzes campaign performance data to provide explanatory insights. It has no side effects on campaign state, bidding, targeting, or ad serving. It does not execute changes, delete data, or trigger financial transactions.
From the tool's definition Tool name and description indicate diagnostic/analytical operation: 'Explains why a campaign is not serving or is under-delivering.' No creation, modification, deletion, or execution of external operations; purely informational analysis of campaign status.
Attacks that exploit this kind of access
The rule that runs google_ads_campaigns_diagnose 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_campaigns_diagnose, this is the rule to start with:
google_ads_campaigns_diagnose 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_campaigns_diagnose call is checked against it from then on.
Questions about google_ads_campaigns_diagnose
Explains why a campaign is not serving or is under-delivering. 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_campaigns_diagnose: 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_campaigns_diagnose 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_campaigns_diagnose 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_campaigns_diagnose. 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_campaigns_diagnose 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