This record as markdown: /tools/creativelead-unclick/foursquare-search-places.md
What foursquare_search_places does on UnClick
AI agents call foursquare_search_places 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 | — | lat,lng |
near | string | — | |
limit | number | — | |
query | string | — | |
api_key | string | — |
Parameters from the server's own tool schema.
Why foursquare_search_places is rated Low
This tool retrieves or queries location data from Foursquare without creating, modifying, deleting, or executing operations. It is a straightforward read operation that returns place information based on search parameters. No reversible or irreversible modifications are possible, nor does it involve code execution or financial transactions.
From the tool's definition Tool name is 'foursquare_search_places' and description states 'Search for places on Foursquare.' The verb 'search' and the action of querying a public location database indicate data retrieval with no side effects.
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_search_places 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_search_places, this is the rule to start with:
foursquare_search_places 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_search_places call is checked against it from then on.
Questions about foursquare_search_places
Search for places on Foursquare. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
foursquare_search_places accepts 5 parameters: ll, near, limit, 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_search_places: 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_search_places 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_search_places 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_search_places. 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_search_places 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