Low Risk

google_ads_keywords_audit

Runs a holistic keyword-portfolio audit for a campaign and

How to control google_ads_keywords_audit ↓

What google_ads_keywords_audit does on Mureo

AI agents call google_ads_keywords_audit 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.

Low Risk

Why google_ads_keywords_audit needs a policy

Auditing is a read-only operation that retrieves and analyzes keyword performance data without creating, modifying, deleting, or executing external commands. The tool queries existing campaign keyword data and generates a report, which is characteristic of Read category tools.

From the tool's definition Tool name 'google_ads_keywords_audit' and description indicate it 'Runs a holistic keyword-portfolio audit' — an inspection/analysis operation with no side effects.

Documented attack patterns abuse exactly the kind of access google_ads_keywords_audit gives an agent:

How to control google_ads_keywords_audit

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_keywords_audit:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "google_ads_keywords_audit": {}
  }
}

google_ads_keywords_audit is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mureo — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about google_ads_keywords_audit

What does the google_ads_keywords_audit tool do? +

Runs a holistic keyword-portfolio audit for a campaign and. 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_keywords_audit? +

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

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

Can I rate-limit google_ads_keywords_audit? +

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

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

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

Enforce policy on every Mureo tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.