valet_search_by_service_and_city
Search valet operators by service slug plus city slug across all matching states. Use this when an agent has both a service slug and a city slug and wants a cross-state tier-then-name ranked list. Invalid service slugs surface the 9 canonical alternatives.
This record as markdown: /tools/com-getvaletparking-valet-parking-directory/valet-search-by-service-and-city.md
What valet_search_by_service_and_city does on Valet Parking Directory
AI agents call valet_search_by_service_and_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max results to return; default 10, capped at 50 |
city_slug | string | Yes | Lowercase kebab-case city slug (e.g. 'austin', 'springfield'). May match multiple cities across states. |
service_slug | string | Yes | Required canonical valet service slug. One of 9 values; call valet_list_services for the full set. |
Parameters from the server's own tool schema.
Why valet_search_by_service_and_city is rated Low
This tool retrieves and queries data from the valet parking directory without side effects. The description indicates it searches and returns information based on parameters (service slug and city slug), which is a pure read operation. The mention of 'Invalid service slugs surface the 9 canonical alternatives' further confirms it is informational/advisory with no data modification.
From the tool's definition Tool performs a 'Search' operation that 'returns a cross-state tier-then-name ranked list' of valet operators matching given service and city parameters. No creation, modification, deletion, or execution capabilities are described.
Attacks that exploit this kind of access
The rule that runs valet_search_by_service_and_city 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_by_service_and_city, this is the rule to start with:
valet_search_by_service_and_city 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_by_service_and_city call is checked against it from then on.
Questions about valet_search_by_service_and_city
Search valet operators by service slug plus city slug across all matching states. Use this when an agent has both a service slug and a city slug and wants a cross-state tier-then-name ranked list. Invalid service slugs surface the 9 canonical alternatives. It is categorised as a Read tool in the Valet Parking Directory MCP Server, which means it retrieves data without modifying state.
valet_search_by_service_and_city accepts 3 parameters: limit, city_slug, service_slug. Required: city_slug, service_slug. 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_by_service_and_city: 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_by_service_and_city 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_by_service_and_city 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_by_service_and_city. 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_by_service_and_city 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