foursquare_get_place
Get details for a Foursquare place by FSQ ID.
This record as markdown: /tools/creativelead-unclick/foursquare-get-place.md
What foursquare_get_place does on UnClick
AI agents call foursquare_get_place 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 |
|---|---|---|---|
fsq_id | string | — | |
api_key | string | — |
Parameters from the server's own tool schema.
Why foursquare_get_place is rated Low
This tool retrieves publicly available place information from Foursquare by ID. It has no side effects, does not modify data, execute code, delete resources, or commit financial transactions. The blast radius of misuse is minimal — an agent could retrieve irrelevant place details but cannot cause harm through this tool alone.
From the tool's definition Tool description states 'Get details for a Foursquare place by FSQ ID' — a retrieval operation with no modification, deletion, or execution of external operations.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs foursquare_get_place 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_get_place, this is the rule to start with:
foursquare_get_place 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_get_place call is checked against it from then on.
Questions about foursquare_get_place
Get details for a Foursquare place by FSQ ID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
foursquare_get_place accepts 2 parameters: fsq_id, 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_get_place: 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_get_place 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_get_place 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_get_place. 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_get_place 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