local_search
Find local businesses, restaurants, services, and places near any location. Returns name, type, address, phone, website, hours, cuisine, and distance. Use this for 'find restaurants near me', 'coffee shops in downtown Houston', 'gas stations near 60601', 'best pizza in Chicago', 'pharmacies nearb...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/local-search.md
What local_search does on Livedatalink
AI agents call local_search to retrieve information from Livedatalink 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 |
|---|---|---|---|
query | string | Yes | What to find (e.g., 'restaurants', 'coffee', 'gas station') |
radius | number | — | Search radius in miles (default: 1.5) |
location | string | Yes | Where to search (city, zip, or address) |
Parameters from the server's own tool schema.
Why local_search is rated Low
This tool performs queries against a local business database to retrieve publicly available information about businesses and places. It has no capability to create, modify, delete, or execute actions—it only searches and returns structured data about businesses. The severity is low because misuse would only result in unwanted information retrieval, not data modification, financial impact, or system compromise.
From the tool's definition Tool description states it 'Find[s] local businesses, restaurants, services, and places near any location' and 'Returns name, type, address, phone, website, hours, cuisine, and distance.' The verb 'find' and 'returns' indicate data retrieval with no…
Attacks that exploit this kind of access
The rule that runs local_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For local_search, this is the rule to start with:
local_search 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 Livedatalink, apply this rule, and every local_search call is checked against it from then on.
Questions about local_search
Find local businesses, restaurants, services, and places near any location. Returns name, type, address, phone, website, hours, cuisine, and distance. Use this for 'find restaurants near me', 'coffee shops in downtown Houston', 'gas stations near 60601', 'best pizza in Chicago', 'pharmacies nearby', 'hotels in Austin', 'find a mechanic', 'gyms near me', or any local business or place discovery question. Supports: restaurants, cafes, bars, gas stations, pharmacies, hospitals, doctors, dentists, gyms, hotels, grocery stores, banks, schools, parks, libraries, auto repair, salons, and more. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
local_search accepts 3 parameters: query, radius, location. Required: query, location. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for local_search: 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 Livedatalink. Nothing to install.
local_search 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 local_search 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 local_search. 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.
local_search is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue