valet_list_services
List the 9 canonical valet service slugs with display name and category. Use this when an agent needs to validate or discover the supported service taxonomy before composing a follow-up search (e.g. valet_search_by_service_and_city). Returns the in-bundle catalog; no upstream call; no isError path.
This record as markdown: /tools/com-getvaletparking-valet-parking-directory/valet-list-services.md
What valet_list_services does on Valet Parking Directory
AI agents call valet_list_services 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.
Why valet_list_services is rated Low
This tool purely retrieves a static, pre-bundled list of service taxonomy slugs. It makes no upstream calls, causes no side effects, and only returns read-only catalog data. Misuse potential is essentially nil.
From the tool's definition List the 9 canonical valet service slugs with display name and category... Returns the in-bundle catalog; no upstream call; no isError path.
Attacks that exploit this kind of access
The rule that runs valet_list_services 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_list_services, this is the rule to start with:
valet_list_services 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_list_services call is checked against it from then on.
Questions about valet_list_services
List the 9 canonical valet service slugs with display name and category. Use this when an agent needs to validate or discover the supported service taxonomy before composing a follow-up search (e.g. valet_search_by_service_and_city). Returns the in-bundle catalog; no upstream call; no isError path. It is categorised as a Read tool in the Valet Parking Directory MCP Server, which means it retrieves data without modifying state.
Register the Valet Parking Directory MCP server in PolicyLayer and add a rule for valet_list_services: 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_list_services 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_list_services 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_list_services. 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_list_services 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