New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

google_ads_cpc_detect_trend

Detect rising/falling CPC trends in a Google Ads campaign

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-cpc-detect-trend.md

What google_ads_cpc_detect_trend does on Mureo

AI agents call google_ads_cpc_detect_trend 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_cpc_detect_trend is rated Low

The tool retrieves and analyzes campaign performance metrics (CPC trends) to identify patterns. This is a passive analytical operation with no side effects on campaign configuration, budgets, ads, or account state. It neither modifies data (Write), executes external commands (Execute), deletes anything (Destructive), nor moves money (Financial).

From the tool's definition Tool performs trend detection on CPC (cost-per-click) metrics—a read-only analysis operation. Description uses 'detect,' implying observation and querying of existing campaign data without modification, creation, or deletion.

Questions about google_ads_cpc_detect_trend

What does the google_ads_cpc_detect_trend tool do? +

Detect rising/falling CPC trends in a Google Ads campaign. 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_cpc_detect_trend? +

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

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

Can I rate-limit google_ads_cpc_detect_trend? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mureo's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.