valet_search_cities
Search the cities directory by name prefix with population-ranked results. Use this when an agent needs to resolve a partial city name into a canonical city slug plus state slug plus lat/lng before composing valet_find_operators_in_city or valet_find_operators_near. Empty array if no matches.
This record as markdown: /tools/com-getvaletparking-valet-parking-directory/valet-search-cities.md
What valet_search_cities does on Valet Parking Directory
AI agents call valet_search_cities 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 |
|---|---|---|---|
limit | integer | — | Max results to return; default 8, capped at 25 |
query | string | Yes | Partial or full city name (>=2 chars). Matched against name and lowercase name fields with prefix semantics. |
Parameters from the server's own tool schema.
Why valet_search_cities is rated Low
This tool queries a public valet parking directory to resolve city names into slugs and coordinates. It performs a simple lookup with zero destructive, financial, or execution capabilities. The data returned is informational and used only to prepare parameters for other tools.
From the tool's definition 'Search the cities directory by name prefix' – retrieves data from a directory; 'Empty array if no matches' – read-only with no side effects; returns canonical city and state identifiers for downstream queries.
Attacks that exploit this kind of access
The rule that runs valet_search_cities 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_search_cities, this is the rule to start with:
valet_search_cities 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_search_cities call is checked against it from then on.
Questions about valet_search_cities
Search the cities directory by name prefix with population-ranked results. Use this when an agent needs to resolve a partial city name into a canonical city slug plus state slug plus lat/lng before composing valet_find_operators_in_city or valet_find_operators_near. Empty array if no matches. It is categorised as a Read tool in the Valet Parking Directory MCP Server, which means it retrieves data without modifying state.
valet_search_cities accepts 2 parameters: limit, query. Required: query. 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_search_cities: 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_search_cities 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_search_cities 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_search_cities. 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_search_cities 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