recreation_search_campsites
Search individual campsites (sites within a campground): loop, accessibility, type, reservable. Provide facility_id to list sites within a known campground, or query to free-text search.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/recreation-search-campsites.md
What recreation_search_campsites does on Livedatalink
AI agents call recreation_search_campsites 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 campsite name. Optional. |
facility_id | string | — | RIDB FacilityID to list campsites within. Optional. |
Parameters from the server's own tool schema.
Why recreation_search_campsites is rated Low
This is a pure data retrieval tool that queries a campsite database and returns structured information to the user. It has no side effects, cannot modify data, execute code, or affect external systems. The search capability is read-only lookup functionality typical of informational APIs.
From the tool's definition Tool performs 'Search' of campsite data with parameters like 'facility_id' and 'query' for filtering/free-text search. Returns campsite information (loop, accessibility, type, reservable status).
Attacks that exploit this kind of access
The rule that runs recreation_search_campsites 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_campsites, this is the rule to start with:
recreation_search_campsites 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_campsites call is checked against it from then on.
Questions about recreation_search_campsites
Search individual campsites (sites within a campground): loop, accessibility, type, reservable. Provide facility_id to list sites within a known campground, or query to free-text search. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
recreation_search_campsites accepts 3 parameters: limit, query, facility_id. 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_campsites: 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_campsites 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_campsites 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_campsites. 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_campsites 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