valet_get_operator
Get the full operator profile by slug including address, phone, website, services, venues_served, FAQs, and tipping note. Use this when an agent has a slug from a search tool or directory URL and needs the complete profile to rank or present. Returns isError on slug 404 or upstream outage.
This record as markdown: /tools/com-getvaletparking-valet-parking-directory/valet-get-operator.md
What valet_get_operator does on Valet Parking Directory
AI agents call valet_get_operator 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 |
|---|---|---|---|
slug | string | Yes | Canonical kebab-case operator slug (e.g. '12-oaks-parking-llc'). Lowercase letters, digits, hyphens only. |
Parameters from the server's own tool schema.
Why valet_get_operator is rated Low
This is a query/lookup operation that retrieves and presents existing profile information about a valet parking operator. No data is created, modified, deleted, or used to execute external commands. The only input is a slug identifier, and output is read-only profile data. This is a straightforward Read category tool with low severity—misuse would only expose publicly available business information.
From the tool's definition Tool retrieves 'full operator profile by slug including address, phone, website, services, venues_served, FAQs, and tipping note' with no modification or side effects described. Returns data or isError on failure.
Attacks that exploit this kind of access
The rule that runs valet_get_operator 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_get_operator, this is the rule to start with:
valet_get_operator 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_get_operator call is checked against it from then on.
Questions about valet_get_operator
Get the full operator profile by slug including address, phone, website, services, venues_served, FAQs, and tipping note. Use this when an agent has a slug from a search tool or directory URL and needs the complete profile to rank or present. Returns isError on slug 404 or upstream outage. It is categorised as a Read tool in the Valet Parking Directory MCP Server, which means it retrieves data without modifying state.
valet_get_operator accepts 1 parameter: slug. Required: 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_get_operator: 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_get_operator 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_get_operator 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_get_operator. 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_get_operator 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