Analyses recent search-term performance and returns suggested
AI agents call google_ads_negative_keywords_suggest 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.
This tool retrieves and analyzes existing search-term performance data to generate suggestions. It has no side effects—it does not create, modify, delete, or execute any changes to Google Ads accounts or campaigns. The incomplete description ('returns suggested' without object) is typical of read-only analysis tools.
From the tool's definition Tool name ends in 'suggest' and description indicates it 'Analyses recent search-term performance and returns suggested' [keywords]. No create, update, delete, execute, or financial operations are mentioned.
Documented attack patterns abuse exactly the kind of access google_ads_negative_keywords_suggest 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_negative_keywords_suggest:
{
"version": "1",
"default": "deny",
"tools": {
"google_ads_negative_keywords_suggest": {}
}
} google_ads_negative_keywords_suggest 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.
Analyses recent search-term performance and returns suggested. 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_negative_keywords_suggest: 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_negative_keywords_suggest 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_negative_keywords_suggest 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_negative_keywords_suggest. 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_negative_keywords_suggest 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.