google_ads_negative_keywords_remove
Removes a single campaign-level negative keyword. Returns the
This record as markdown: /tools/logly-mureo/google-ads-negative-keywords-remove.md
What google_ads_negative_keywords_remove does on Mureo
AI agents call google_ads_negative_keywords_remove to permanently remove resources in Mureo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why google_ads_negative_keywords_remove is rated Critical
The tool irreversibly deletes a negative keyword configuration from a Google Ads campaign. Negative keywords are critical ad-targeting controls; removing them cannot be undone through the tool itself and will directly alter campaign behavior and ad spend allocation. This is an irreversible data deletion operation affecting live advertising infrastructure, justifying Destructive classification with high severity.
From the tool's definition Removes a single campaign-level negative keyword. Returns the...
Attacks that exploit this kind of access
The rule that runs google_ads_negative_keywords_remove 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_negative_keywords_remove, this is the rule to start with:
google_ads_negative_keywords_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mureo, apply this rule, and every google_ads_negative_keywords_remove call is checked against it from then on.
Questions about google_ads_negative_keywords_remove
Removes a single campaign-level negative keyword. Returns the. It is categorised as a Destructive tool in the Mureo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mureo MCP server in PolicyLayer and add a rule for google_ads_negative_keywords_remove: 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_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the google_ads_negative_keywords_remove 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_remove. 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_remove 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.
Across the catalogue