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.
This record as markdown: /tools/com-getvaletparking-valet-parking-directory/valet-find-operators-in-city.md
What valet_find_operators_in_city does on Valet Parking Directory
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
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 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.
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 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.
Attacks that exploit this kind of access
The rule that runs valet_find_operators_in_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_find_operators_in_city, this is the rule to start with:
valet_find_operators_in_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_find_operators_in_city call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Valet Parking Directory MCP Server, which means it retrieves data without modifying state.
valet_find_operators_in_city accepts 4 parameters: limit, service, city_slug, state_slug. Required: city_slug, state_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_find_operators_in_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_find_operators_in_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_find_operators_in_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_find_operators_in_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_find_operators_in_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