GOOGLESUPER_GET_CAMPAIGN_BY_NAME
GetCampaignByName Tool will run a SQL GetCampaignByName in Google Ads.
This record as markdown: /tools/googlesuper/googlesuper-get-campaign-by-name.md
What GOOGLESUPER_GET_CAMPAIGN_BY_NAME does on Google Super
AI agents call GOOGLESUPER_GET_CAMPAIGN_BY_NAME to retrieve information from Google Super without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | name of the campaign to search on GoogleAds. |
Parameters from the server's own tool schema.
Why GOOGLESUPER_GET_CAMPAIGN_BY_NAME is rated Low
This tool queries campaign information from Google Ads, which is a read-only retrieval operation. There are no side effects, data modifications, deletions, financial transactions, or code execution involved. The blast radius of misuse is minimal — an agent could retrieve campaign names and associated data, which may have privacy implications but cannot directly harm systems or cause irreversible changes.
From the tool's definition Tool description states it will 'run a SQL GetCampaignByName in Google Ads' — the GetCampaignByName operation is a retrieval/query operation that fetches campaign data by name without modifying or deleting resources.
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_GET_CAMPAIGN_BY_NAME safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Super, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For GOOGLESUPER_GET_CAMPAIGN_BY_NAME, this is the rule to start with:
GOOGLESUPER_GET_CAMPAIGN_BY_NAME 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 Google Super, apply this rule, and every GOOGLESUPER_GET_CAMPAIGN_BY_NAME call is checked against it from then on.
Questions about GOOGLESUPER_GET_CAMPAIGN_BY_NAME
GetCampaignByName Tool will run a SQL GetCampaignByName in Google Ads. It is categorised as a Read tool in the Google Super MCP Server, which means it retrieves data without modifying state.
GOOGLESUPER_GET_CAMPAIGN_BY_NAME accepts 1 parameter: name. The full parameter table on this page comes from the server's own tool schema.
Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_GET_CAMPAIGN_BY_NAME: 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 Google Super. Nothing to install.
GOOGLESUPER_GET_CAMPAIGN_BY_NAME 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 GOOGLESUPER_GET_CAMPAIGN_BY_NAME 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 GOOGLESUPER_GET_CAMPAIGN_BY_NAME. 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.
GOOGLESUPER_GET_CAMPAIGN_BY_NAME is provided by the Google Super MCP server (googlesuper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Super, and thousands of servers like it.
This server
Across the catalogue