googleAds_get_geo_performance
Get performance metrics broken down by geographic location
This record as markdown: /tools/io-github-alifanov-scopegate/googleads-get-geo-performance.md
What googleAds_get_geo_performance does on ScopeGate
AI agents call googleAds_get_geo_performance to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why googleAds_get_geo_performance is rated Low
This tool retrieves and queries performance data segmented by geographic location. There are no side effects, data modifications, code execution, deletions, or financial transactions. It is a straightforward data retrieval operation with minimal risk if misused by an agent—the worst outcome would be exposure of performance analytics that the agent already has permission to access.
From the tool's definition Tool name 'googleAds_get_geo_performance' and description 'Get performance metrics broken down by geographic location' indicate data retrieval without modification.
Attacks that exploit this kind of access
The rule that runs googleAds_get_geo_performance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For googleAds_get_geo_performance, this is the rule to start with:
googleAds_get_geo_performance 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 ScopeGate, apply this rule, and every googleAds_get_geo_performance call is checked against it from then on.
Questions about googleAds_get_geo_performance
Get performance metrics broken down by geographic location. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.
Register the ScopeGate MCP server in PolicyLayer and add a rule for googleAds_get_geo_performance: 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 ScopeGate. Nothing to install.
googleAds_get_geo_performance 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 googleAds_get_geo_performance 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 googleAds_get_geo_performance. 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.
googleAds_get_geo_performance is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue