# 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.

Agent View of the PolicyLayer registry record for `GOOGLESUPER_GEOCODING_API`. HTML page: https://policylayer.com/tools/googlesuper/googlesuper-geocoding-api

## Facts

- Tool: `GOOGLESUPER_GEOCODING_API`
- Server: Google Super (`googlesuper`) — https://policylayer.com/tools/googlesuper.md
- Install: `npx -y googlesuper`
- Homepage: https://www.npmjs.com/package/googlesuper
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 11
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `key` | string | no | Your application's API key. If not provided, will be extracted from connection metadata. |
| `bounds` | string | no | 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 | no | 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 | no | 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 | no | The street address or plus code that you want to geocode. Provide for geocoding (address to coordinates). |
| `language` | string | no | 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 | no | The place ID of the place for which you wish to obtain the human-readable address. Provide for place ID geocoding. |
| `components` | string | no | 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 | no | 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 | no | 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 | no | Use this parameter to specify additional features in the response. Can select multiple values. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "GOOGLESUPER_GEOCODING_API",
    "arguments": {}
  }
}
```

## 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 own 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 signals: High parameter count (11 properties)

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Google Super:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "GOOGLESUPER_GEOCODING_API": {}
  }
}
```

## Other tools on Google Super (199)

- `GOOGLESUPER_BATCH_DELETE_MESSAGES` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-batch-delete-messages.md
- `GOOGLESUPER_CALENDARS_DELETE` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-calendars-delete.md
- `GOOGLESUPER_CLEAR_BASIC_FILTER` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-clear-basic-filter.md
- `GOOGLESUPER_CLEAR_CALENDAR` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-clear-calendar.md
- `GOOGLESUPER_CLEAR_TASKS` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-clear-tasks.md
- `GOOGLESUPER_CLEAR_VALUES` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-clear-values.md
- `GOOGLESUPER_DELETE_COMMENT` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-comment.md
- `GOOGLESUPER_DELETE_CONTENT_RANGE` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-content-range.md
- `GOOGLESUPER_DELETE_DIMENSION` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-dimension.md
- `GOOGLESUPER_DELETE_DRAFT` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-draft.md
- `GOOGLESUPER_DELETE_DRIVE` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-drive.md
- `GOOGLESUPER_DELETE_EVENT` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-event.md
- `GOOGLESUPER_DELETE_FOOTER` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-footer.md
- `GOOGLESUPER_DELETE_HEADER` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-header.md
- `GOOGLESUPER_DELETE_MESSAGE` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-message.md
- `GOOGLESUPER_DELETE_NAMED_RANGE` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-named-range.md
- `GOOGLESUPER_DELETE_PERMISSION` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-permission.md
- `GOOGLESUPER_DELETE_REPLY` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-reply.md
- `GOOGLESUPER_DELETE_SHEET` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-sheet.md
- `GOOGLESUPER_DELETE_TABLE` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-table.md
- `GOOGLESUPER_DELETE_TABLE_COLUMN` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-table-column.md
- `GOOGLESUPER_DELETE_TABLE_ROW` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-table-row.md
- `GOOGLESUPER_DELETE_TASK` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-task.md
- `GOOGLESUPER_DELETE_TASK_LIST` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-task-list.md
- `GOOGLESUPER_EMPTY_TRASH` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-empty-trash.md
- `GOOGLESUPER_GOOGLE_DRIVE_DELETE_FOLDER_OR_FILE_ACTION` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-google-drive-delete-folder-or-file-action.md
- `GOOGLESUPER_MOVE_TO_TRASH` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-move-to-trash.md
- `GOOGLESUPER_EVENTS_WATCH` — Execute — https://policylayer.com/tools/googlesuper/googlesuper-events-watch.md
- `GOOGLESUPER_EXECUTE_SQL` — Execute — https://policylayer.com/tools/googlesuper/googlesuper-execute-sql.md
- `GOOGLESUPER_QUERY_TABLE` — Execute — https://policylayer.com/tools/googlesuper/googlesuper-query-table.md
- …and 169 more: https://policylayer.com/tools/googlesuper.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=googlesuper · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/googlesuper