foursquare_autocomplete
Autocomplete a Foursquare place search.
This record as markdown: /tools/creativelead-unclick/foursquare-autocomplete.md
What foursquare_autocomplete does on UnClick
AI agents call foursquare_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 |
|---|---|---|---|
ll | string | — | |
query | string | — | |
api_key | string | — |
Parameters from the server's own tool schema.
Why foursquare_autocomplete is rated Low
Autocomplete is a read-only operation that queries a search API to return matching place suggestions. It has no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions. The narrow scope and predictable behavior typical of autocomplete functions present minimal security risk.
From the tool's definition Tool performs 'autocomplete a Foursquare place search' - a query operation that retrieves suggestions without modifying data or triggering external actions.
Risk signalsAccepts freeform code/query input (query) · Handles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs foursquare_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 foursquare_autocomplete, this is the rule to start with:
foursquare_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 foursquare_autocomplete call is checked against it from then on.
Questions about foursquare_autocomplete
Autocomplete a Foursquare place search. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
foursquare_autocomplete accepts 3 parameters: ll, query, api_key. 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 foursquare_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.
foursquare_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 foursquare_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 foursquare_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.
foursquare_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