google_ads_list_extensions
AI agents call google_ads_list_extensions to retrieve information from Google Ads MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves extension data from Google Ads accounts (likely ad extensions such as callouts, sitelinks, or structured snippets based on sibling tools). It performs no side effects—no campaign modification, no financial transactions, and no destructive actions.
From the tool's definition Tool name 'google_ads_list_extensions' indicates a listing/retrieval operation. The 'list_' prefix is characteristic of Read operations that query data without modification.
Attacks that exploit this kind of access
google_ads_list_extensions. It is categorised as a Read tool in the Google Ads MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Ads MCP Server MCP server in PolicyLayer and add a rule for google_ads_list_extensions: 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 Ads MCP Server. Nothing to install.
google_ads_list_extensions 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_list_extensions 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_list_extensions. 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_list_extensions is provided by the Google Ads MCP Server MCP server (mikdeangelis/mcp-google-ads). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →