# compute_routes

Computes a travel route between a specified origin and destination. Supported Travel Modes: DRIVE (default), WALK. Input Requirements (CRITICAL): Requires both origin and destination. Each must be provided using one of the following methods, nested within its respective field: * address: (string, e.g., 'Eiffel Tower, Paris'). Note: The more granular or specific the input address is, the better the results will be. * lat_lng: (object, {"latitude": number, "longitude": number}) * place_id: (string, e.g., 'ChIJOwE_Id1w5EAR4Q27FkL6T_0') Note: This id can be obtained from the search_places tool. Any combination of input types is allowed (e.g., origin by address, destination by lat_lng). If either the origin or destination is missing, you MUST ask the user for clarification before attempting to call the tool. Example Tool Call: {"origin":{"address":"Eiffel Tower"},"destination":{"place_id":"ChIJt_5xIthw5EARoJ71mGq7t74"},"travel_mode":"DRIVE"} * The grounded output must be attributed to the source using the information from the attribution field when available.

Agent View of the PolicyLayer registry record for `compute_routes`. HTML page: https://policylayer.com/tools/com-googleapis-mapstools-mcp/compute-routes

## Facts

- Tool: `compute_routes`
- Server: Mcp (`https://mapstools.googleapis.com/mcp`) — https://policylayer.com/tools/com-googleapis-mapstools-mcp.md
- Homepage: https://github.com/https://mapstools.googleapis.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 3 (2 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `origin` | object | yes | Required. Origin waypoint. |
| `travelMode` | string | no | Optional. Specifies the mode of transportation. |
| `destination` | object | yes | Required. Destination waypoint. |

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": "compute_routes",
    "arguments": {
      "origin": {},
      "destination": {}
    }
  }
}
```

## Why compute_routes is rated Low

This tool queries geospatial data and returns computed route information based on provided parameters. It has no side effects, does not modify data, does not execute arbitrary code or commands, and does not perform destructive or financial operations. It is a straightforward data retrieval function typical of mapping APIs.

From the tool's own definition: "Tool description states it 'Computes a travel route' between origin and destination with supported travel modes (DRIVE, WALK). Input requirements show it accepts address, lat_lng, or place_id parameters."

Risk signals: Accepts file system path (destination)

## Use case

AI agents call compute_routes to retrieve information from Mcp 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 Mcp:

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

## Other tools on Mcp (4)

- `lookup_weather` — Read — https://policylayer.com/tools/com-googleapis-mapstools-mcp/lookup-weather.md
- `resolve_maps_urls` — Read — https://policylayer.com/tools/com-googleapis-mapstools-mcp/resolve-maps-urls.md
- `resolve_names` — Read — https://policylayer.com/tools/com-googleapis-mapstools-mcp/resolve-names.md
- `search_places` — Read — https://policylayer.com/tools/com-googleapis-mapstools-mcp/search-places.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=com-googleapis-mapstools-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-googleapis-mapstools-mcp