List all Conversion Actions for the account
AI agents call get_conversion_actions 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 queries and retrieves existing conversion action metadata from a Google Ads account. It has no side effects, does not execute operations, does not modify data, and does not involve financial transactions. The blast radius of misuse is limited to information disclosure of conversion tracking configuration.
From the tool's definition Tool name 'get_conversion_actions' uses the 'get' verb and description states 'List all Conversion Actions' — a pure data retrieval operation with no modification, deletion, or execution.
Attacks that exploit this kind of access
List all Conversion Actions for the account. 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 get_conversion_actions: 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.
get_conversion_actions 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 get_conversion_actions 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 get_conversion_actions. 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.
get_conversion_actions is provided by the Google Ads MCP Server MCP server (samihalawa/google-ads-mcp-server). 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 →