# valet_request_quote

Submit a valet parking quote request to the operators serving a US city. Use this when a person has asked you to arrange valet and has given their name, email, phone, city, service type and event date. The request is only sent after they confirm by email.

Agent View of the PolicyLayer registry record for `valet_request_quote`. HTML page: https://policylayer.com/tools/com-getvaletparking-valet-parking-directory/valet-request-quote

## Facts

- Tool: `valet_request_quote`
- 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: 11 (5 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `notes` | string | no | Free-text notes for the operator, e.g. venue name or timing details |
| `service` | string | yes | One of the 9 canonical valet service slugs |
| `city_slug` | string | no | Canonical kebab-case city slug from valet_search_cities, e.g. 'austin'. Omit if using city_other. |
| `city_other` | string | no | Free-text city name when no directory slug is known. Omit if using city_slug. |
| `event_date` | string | yes | Event date in YYYY-MM-DD format |
| `guest_count` | integer | no | Approximate guest count, if known |
| `contact_name` | string | yes | The requester's full name |
| `contact_email` | string | yes | Email address to send the one-tap confirmation link to |
| `contact_phone` | string | yes | Phone number the operator can call |
| `operator_slug` | string | no | Send to this one operator only instead of the full fan-out for the city. Omit to notify every matched operator in the city. |
| `vehicle_count` | integer | no | Approximate vehicle count, if known |

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_request_quote",
    "arguments": {
      "service": "<service>",
      "event_date": "<event_date>",
      "contact_name": "<contact_name>",
      "contact_email": "<contact_email>",
      "contact_phone": "<contact_phone>"
    }
  }
}
```

## Why valet_request_quote is rated Low

Even though valet_request_quote only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signals: High parameter count (11 properties)

## Use case

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

## Other tools on Valet Parking Directory (7)

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