recreation_nearby
List federal recreation facilities within a radius of a coordinate. Useful for proximity searches (e.g. campgrounds near a property, fishing spots near a city). Radius is in kilometers.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/recreation-nearby.md
What recreation_nearby does on Livedatalink
AI agents call recreation_nearby 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 |
|---|---|---|---|
lat | number | Yes | Center latitude. |
lon | number | Yes | Center longitude. |
limit | number | — | Max rows (1-50, default 10). |
activity | string | — | Optional activity filter. |
radius_km | number | — | Radius in kilometers (default 30, max ~320). |
Parameters from the server's own tool schema.
Why recreation_nearby is rated Low
Even though recreation_nearby only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs recreation_nearby 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 recreation_nearby, this is the rule to start with:
recreation_nearby 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 recreation_nearby call is checked against it from then on.
Questions about recreation_nearby
List federal recreation facilities within a radius of a coordinate. Useful for proximity searches (e.g. campgrounds near a property, fishing spots near a city). Radius is in kilometers. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
recreation_nearby accepts 5 parameters: lat, lon, limit, activity, radius_km. Required: lat, lon. 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 recreation_nearby: 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.
recreation_nearby 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 recreation_nearby 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 recreation_nearby. 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.
recreation_nearby 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