DEPRECATED: Legacy API to convert addresses into geographic coordinates (latitude and longitude) and vice versa (reverse geocoding), or get an address for a Place ID. This API only works with API keys (no OAuth2 support). Consider using the modern Places API (Text Search or Nearby Search) for sim...
High parameter count (11 properties)
Part of the Google Super MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call GOOGLESUPER_GEOCODING_API to retrieve information from Google Super without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though GOOGLESUPER_GEOCODING_API only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
GOOGLESUPER_GEOCODING_API:
rules:
- action: allowSee the full Google Super policy for all 200 tools.
DEPRECATED: Legacy API to convert addresses into geographic coordinates (latitude and longitude) and vice versa (reverse geocoding), or get an address for a Place ID. This API only works with API keys (no OAuth2 support). Consider using the modern Places API (Text Search or Nearby Search) for similar functionality with OAuth2 authentication.. It is categorised as a Read tool in the Google Super MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for GOOGLESUPER_GEOCODING_API. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Google Super MCP server.
GOOGLESUPER_GEOCODING_API 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 GOOGLESUPER_GEOCODING_API rule in your Intercept 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 Intercept policy for GOOGLESUPER_GEOCODING_API. 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.
GOOGLESUPER_GEOCODING_API is provided by the Google Super MCP server (googlesuper). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept