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.
This record as markdown: /tools/com-getvaletparking-valet-parking-directory/valet-find-nearest-operators.md
What valet_find_nearest_operators does on Valet Parking Directory
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.
| 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 | — | Max results to return; default 10, capped at 50 |
service | string | — | 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.
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 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.
Attacks that exploit this kind of access
The rule that runs valet_find_nearest_operators safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Valet Parking Directory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For valet_find_nearest_operators, this is the rule to start with:
valet_find_nearest_operators is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Valet Parking Directory, apply this rule, and every valet_find_nearest_operators call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Valet Parking Directory MCP Server, which means it retrieves data without modifying state.
valet_find_nearest_operators accepts 4 parameters: lat, lng, limit, service. Required: lat, lng. The full parameter table on this page comes from the server's own tool schema.
Register the Valet Parking Directory MCP server in PolicyLayer and add a rule for valet_find_nearest_operators: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Valet Parking Directory. Nothing to install.
valet_find_nearest_operators is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the valet_find_nearest_operators rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for valet_find_nearest_operators. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
valet_find_nearest_operators is provided by the Valet Parking Directory MCP server (https://api.getvaletparking.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Valet Parking Directory, and thousands of servers like it.
This server
Across the catalogue