GOOGLESUPER_GEOCODING_API
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...
This record as markdown: /tools/googlesuper/googlesuper-geocoding-api.md
What GOOGLESUPER_GEOCODING_API does on Google Super
AI agents call GOOGLESUPER_GEOCODING_API to retrieve information from Google Super without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | — | Your application's API key. If not provided, will be extracted from connection metadata. |
bounds | string | — | The bounding box of the viewport within which to bias geocode results more prominently (e.g., '34.172684,-118.604794|34.236144,-118.500938'). This parameter wil |
latlng | string | — | The latitude and longitude coordinates specifying the location for which you want the closest, human-readable address (e.g., '40.714224,-73.961452'). Provide fo |
region | string | — | The region code, specified as a ccTLD ('top-level domain') two-character value. This parameter will only influence, not fully restrict, results from the geocode |
address | string | — | The street address or plus code that you want to geocode. Provide for geocoding (address to coordinates). |
language | string | — | The language in which to return results. If language is not supplied, the geocoder attempts to use the preferred language as specified in the Accept-Language he |
place_id | string | — | The place ID of the place for which you wish to obtain the human-readable address. Provide for place ID geocoding. |
components | string | — | A components filter with elements separated by a pipe (|). E.g., 'postal_code:94043|country:US'. Used for geocoding, can be restrictive or biasing. |
result_type | string | — | A filter of one or more address types, separated by a pipe (|) (e.g., 'street_address|locality'). Used for reverse geocoding and place ID geocoding. |
location_type | string | — | A filter of one or more location types, separated by a pipe (|) (e.g., 'ROOFTOP|RANGE_INTERPOLATED'). Used for reverse geocoding and place ID geocoding. |
extra_computations | array | — | Use this parameter to specify additional features in the response. Can select multiple values. |
Parameters from the server's own tool schema.
Why GOOGLESUPER_GEOCODING_API is rated Low
The tool retrieves geographic data (coordinates, addresses) based on input queries. Although it uses legacy/deprecated API with API key authentication, it performs no destructive, financial, or state-changing operations. The main risk is data exposure if API credentials are compromised, but the tool itself is a read-only lookup service.
From the tool's definition Tool converts 'addresses into geographic coordinates' and performs 'reverse geocoding' or retrieves 'an address for a Place ID' — these are pure data retrieval operations with no modification or side effects.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_GEOCODING_API safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Super, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For GOOGLESUPER_GEOCODING_API, this is the rule to start with:
GOOGLESUPER_GEOCODING_API 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 Google Super, apply this rule, and every GOOGLESUPER_GEOCODING_API call is checked against it from then on.
Questions about GOOGLESUPER_GEOCODING_API
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.
GOOGLESUPER_GEOCODING_API accepts 11 parameters: key, bounds, latlng, region, address, language, place_id, components, result_type, location_type, extra_computations. The full parameter table on this page comes from the server's own tool schema.
Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_GEOCODING_API: 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 Super. Nothing to install.
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 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 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). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Super, and thousands of servers like it.
This server
Across the catalogue