# valet_find_operators_in_city

List valet operators serving a city slug plus state slug, optionally narrowed by service. Use this when an agent has a city already disambiguated and wants its operator roster ranked premium tier first then name. Empty array if no listed operators.

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

## Facts

- Tool: `valet_find_operators_in_city`
- 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 |
| --- | --- | --- | --- |
| `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 serving the city. |
| `city_slug` | string | yes | Lowercase kebab-case city slug (e.g. 'houston', 'san-francisco') |
| `state_slug` | string | yes | Lowercase kebab-case US state slug (e.g. 'tx', 'new-york') |

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_in_city",
    "arguments": {
      "city_slug": "<city_slug>",
      "state_slug": "<state_slug>"
    }
  }
}
```

## Why valet_find_operators_in_city is rated Low

This tool queries and retrieves a list of valet operators for a given city, with optional filtering by service type. It has no side effects—it does not create, modify, delete, or execute operations. The action is purely informational lookup, making it a Read operation with low severity since misuse would only result in exposing publicly available directory information about parking operators.

From the tool's own definition: "Tool description states it 'List valet operators' and 'returns' an operator roster (or empty array). The verb 'list' and the output being a roster with no modification capability indicate data retrieval."

## Use case

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

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