recreation_search_facilities
Search US federal recreation facilities (campgrounds, picnic areas, trailheads, marinas, visitor centers) across NPS, USFS, BLM, USACE, BOR, FWS. Filter by name, state, or activity (e.g. 'CAMPING', 'FISHING', 'HIKING').
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/recreation-search-facilities.md
What recreation_search_facilities does on Livedatalink
AI agents call recreation_search_facilities 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 |
|---|---|---|---|
limit | number | — | Max rows (1-50, default 10). |
query | string | — | Free-text match on facility name. |
state | string | — | Two-letter state code, e.g. 'CA'. |
activity | string | — | Activity name (CAMPING, FISHING, HIKING, etc.). |
Parameters from the server's own tool schema.
Why recreation_search_facilities is rated Low
This is a straightforward query/search tool that retrieves public information about recreation facilities. It has no side effects, cannot modify data, and poses minimal risk even if misused by an AI agent—the worst outcome would be returning irrelevant search results or excessive API calls. Classified as Read with low severity.
From the tool's definition Tool performs 'Search' operation across federal recreation facilities with filter options (name, state, activity). No modification, deletion, or execution capabilities described. Returns informational data about campgrounds, picnic areas, trailheads, etc.
Attacks that exploit this kind of access
The rule that runs recreation_search_facilities 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_search_facilities, this is the rule to start with:
recreation_search_facilities 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_search_facilities call is checked against it from then on.
Questions about recreation_search_facilities
Search US federal recreation facilities (campgrounds, picnic areas, trailheads, marinas, visitor centers) across NPS, USFS, BLM, USACE, BOR, FWS. Filter by name, state, or activity (e.g. 'CAMPING', 'FISHING', 'HIKING'). It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
recreation_search_facilities accepts 4 parameters: limit, query, state, activity. 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_search_facilities: 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_search_facilities 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_search_facilities 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_search_facilities. 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_search_facilities 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