recreation_facility_detail
Full record for a single federal recreation facility by its RIDB FacilityID: contact, GPS, reservation URL, accessibility, agency.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/recreation-facility-detail.md
What recreation_facility_detail does on Livedatalink
AI agents call recreation_facility_detail 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 |
|---|---|---|---|
facility_id | string | Yes | RIDB FacilityID, e.g. '234064'. |
Parameters from the server's own tool schema.
Why recreation_facility_detail is rated Low
This tool queries and returns public information about federal recreation facilities from the RIDB (Recreation Information Database) by facility ID. It performs a lookup operation with no capability to modify, delete, or execute actions. The data returned (contact info, GPS coordinates, URLs, accessibility details) is factual reference information.
From the tool's definition Tool description states it retrieves 'Full record for a single federal recreation facility' with contact, GPS, reservation URL, accessibility, and agency information.
Attacks that exploit this kind of access
The rule that runs recreation_facility_detail 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_facility_detail, this is the rule to start with:
recreation_facility_detail 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_facility_detail call is checked against it from then on.
Questions about recreation_facility_detail
Full record for a single federal recreation facility by its RIDB FacilityID: contact, GPS, reservation URL, accessibility, agency. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
recreation_facility_detail accepts 1 parameter: facility_id. Required: 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_facility_detail: 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_facility_detail 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_facility_detail 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_facility_detail. 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_facility_detail 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