# valet_find_operators_near

Find valet operators within a given radius of a coordinate, ranked premium tier first then distance. Use this when you have a coordinate and an event-context radius (5mi single venue, 25mi metro, 50mi regional). radius_miles is required; empty array if no matches.

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

## Facts

- Tool: `valet_find_operators_near`
- 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: 5 (3 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 operator within radius regardless of services offered. |
| `radius_miles` | number | yes | Search radius in miles. REQUIRED, no default. Pick based on context: 5 mi for a single venue, 25 mi for a metro, 50 mi for a regional sweep. |

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

## Why valet_find_operators_near is rated Low

This is a straightforward geospatial search tool that retrieves and ranks existing valet operator data based on location parameters. It performs no modifications, deletions, code execution, or financial transactions. The blast radius of misuse is minimal—an attacker could only enumerate valet operators in geographic areas, which is already public business data. Appropriate classification is Read with low severity.

From the tool's own definition: "Tool description explicitly states it 'finds' valet operators and returns results (potentially empty array if no matches), with no mention of creating, modifying, deleting, or executing operations."

## Use case

AI agents call valet_find_operators_near 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_operators_near": {}
  }
}
```

## Other tools on Valet Parking Directory (6)

- `valet_find_nearest_operators` — Read — https://policylayer.com/tools/com-getvaletparking-valet-parking-directory/valet-find-nearest-operators.md
- `valet_find_operators_in_city` — Read — https://policylayer.com/tools/com-getvaletparking-valet-parking-directory/valet-find-operators-in-city.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