This record as markdown: /tools/creativelead-unclick/yelp-autocomplete.md
What yelp_autocomplete does on UnClick
AI agents call yelp_autocomplete to retrieve information from UnClick 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 |
|---|---|---|---|
text | string | — | |
api_key | string | — | |
latitude | number | — | |
longitude | number | — |
Parameters from the server's own tool schema.
Why yelp_autocomplete is rated Low
This tool queries Yelp's autocomplete API to retrieve suggested business names or search terms based on user input. It retrieves data only and produces no side effects, persistent changes, or external actions. This is a standard read operation.
From the tool's definition Tool name 'yelp_autocomplete' and description 'Autocomplete a Yelp business search' indicate retrieval of search suggestions without modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs yelp_autocomplete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For yelp_autocomplete, this is the rule to start with:
yelp_autocomplete 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 UnClick, apply this rule, and every yelp_autocomplete call is checked against it from then on.
Questions about yelp_autocomplete
Autocomplete a Yelp business search. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
yelp_autocomplete accepts 4 parameters: text, api_key, latitude, longitude. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for yelp_autocomplete: 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 UnClick. Nothing to install.
yelp_autocomplete 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 yelp_autocomplete 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 yelp_autocomplete. 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.
yelp_autocomplete is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue