# valet_find_nearest_operators

List nearest valet operators within a 100-mile cap of a coordinate, optionally narrowed by service. Use this when a user is in a city with no listed operators and you need the closest available fallback ranked nearest-first. Empty array if nothing within 100 miles.

Agent View of the PolicyLayer registry record for `valet_find_nearest_operators`. HTML page: https://policylayer.com/tools/com-getvaletparking-valet-parking-directory/valet-find-nearest-operators

## Facts

- Tool: `valet_find_nearest_operators`
- Server: Valet Parking Directory (`https://api.getvaletparking.com/mcp`) — https://policylayer.com/tools/com-getvaletparking-valet-parking-directory.md
- Homepage: https://github.com/getvaletparking/valet-parking-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 4 (2 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `lat` | number | yes | Latitude in decimal degrees (WGS84). Range: -90 to 90. |
| `lng` | number | yes | Longitude in decimal degrees (WGS84). Range: -180 to 180. |
| `limit` | integer | no | Max results to return; default 10, capped at 50 |
| `service` | string | no | Optional service narrowing. One of the 9 canonical valet service slugs. Omit to list every nearby operator regardless of services offered. |

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": "valet_find_nearest_operators",
    "arguments": {
      "lat": 0,
      "lng": 0
    }
  }
}
```

## Why valet_find_nearest_operators is rated Low

This tool retrieves and filters existing valet operator directory data based on geographic proximity and optional service filters. It performs a read-only search operation with no side effects, matching the 'Read' category definition (retrieves or queries data; no side effects). Severity is low because exposure of directory information about valet operators poses minimal risk even if misused by an AI agent.

From the tool's own definition: "Tool description states it 'List[s] nearest valet operators' - a query operation with 'Empty array if nothing within 100 miles' indicating pure data retrieval. No mutation, deletion, execution, or financial operations are mentioned."

## Use case

AI agents call valet_find_nearest_operators to retrieve information from Valet Parking Directory 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 Valet Parking Directory:

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

## Other tools on Valet Parking Directory (6)

- `valet_find_operators_in_city` — Read — https://policylayer.com/tools/com-getvaletparking-valet-parking-directory/valet-find-operators-in-city.md
- `valet_find_operators_near` — Read — https://policylayer.com/tools/com-getvaletparking-valet-parking-directory/valet-find-operators-near.md
- `valet_get_operator` — Read — https://policylayer.com/tools/com-getvaletparking-valet-parking-directory/valet-get-operator.md
- `valet_list_services` — Read — https://policylayer.com/tools/com-getvaletparking-valet-parking-directory/valet-list-services.md
- `valet_search_by_service_and_city` — Read — https://policylayer.com/tools/com-getvaletparking-valet-parking-directory/valet-search-by-service-and-city.md
- `valet_search_cities` — Read — https://policylayer.com/tools/com-getvaletparking-valet-parking-directory/valet-search-cities.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-getvaletparking-valet-parking-directory · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-getvaletparking-valet-parking-directory