Check ad approval and policy status.
AI agents call google_ads_check_ad_approval_status 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 the approval and policy status of ads—a read-only operation with no side effects. It queries existing data about ad compliance and status but does not create, modify, delete, or execute campaigns. The low severity reflects minimal blast radius if misused by an AI agent, as it only exposes informational data about existing ads.
From the tool's definition Tool name 'check_ad_approval_status' and description 'Check ad approval and policy status' indicate a query operation that retrieves status information without modifying, deleting, or executing actions that would change campaign state.
Documented attack patterns abuse exactly the kind of access google_ads_check_ad_approval_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Ads MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for google_ads_check_ad_approval_status:
{
"version": "1",
"default": "deny",
"tools": {
"google_ads_check_ad_approval_status": {}
}
} google_ads_check_ad_approval_status 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.
Check ad approval and policy status. 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_check_ad_approval_status: 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_check_ad_approval_status 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_check_ad_approval_status 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_check_ad_approval_status. 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_check_ad_approval_status is provided by the Google Ads MCP Server MCP server (johnoconnor0/google-ads-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Ads MCP Server, 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.
142 Google Ads MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.