Low Risk

get_cache_stats

REQUIRED for checking media cache status and storage usage. Use this tool when users ask about cache statistics, storage space used by cached media (images and videos), or how many files have been analyzed and cached. Essential for cache management and monitoring.

How to control get_cache_stats ↓

What get_cache_stats does on Google Ads MCP Server

AI agents call get_cache_stats 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.

Low Risk

Why get_cache_stats needs a policy

This tool retrieves cache statistics and storage usage information. It performs a query operation that reads metrics about the cache without modifying, deleting, or executing any actions. No side effects occur from calling this tool. This is a clear Read operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool description states it is 'REQUIRED for checking media cache status and storage usage' and 'how many files have been analyzed and cached.' The verbs 'checking' and 'status' indicate data retrieval with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_cache_stats gives an agent:

How to control get_cache_stats

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 get_cache_stats:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_cache_stats": {}
  }
}

get_cache_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Google Ads MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_cache_stats

What does the get_cache_stats tool do? +

REQUIRED for checking media cache status and storage usage. Use this tool when users ask about cache statistics, storage space used by cached media (images and videos), or how many files have been analyzed and cached. Essential for cache management and monitoring. It is categorised as a Read tool in the Google Ads MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_cache_stats? +

Register the Google Ads MCP Server MCP server in PolicyLayer and add a rule for get_cache_stats: 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.

What risk level is get_cache_stats? +

get_cache_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_cache_stats? +

Yes. Add a rate_limit block to the get_cache_stats 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.

How do I block get_cache_stats completely? +

Set action: deny in the PolicyLayer policy for get_cache_stats. 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.

What MCP server provides get_cache_stats? +

get_cache_stats is provided by the Google Ads MCP Server MCP server (proxy-intell/google-ads-library-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Google Ads MCP Server tool call.

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.

7 Google Ads MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.