recreation_search_recareas
Search federal recreation AREAS (broader units: a whole national forest, a national park unit, a BLM management area) by name, state, or activity. For higher-level place search use this; for specific facilities (campgrounds, trailheads) use recreation_search_facilities.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/recreation-search-recareas.md
What recreation_search_recareas does on Livedatalink
AI agents call recreation_search_recareas 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 recreation-area name. |
state | string | — | Two-letter state code. |
activity | string | — | Activity name. |
Parameters from the server's own tool schema.
Why recreation_search_recareas is rated Low
The tool retrieves or queries publicly available data about federal recreation areas. It has no side effects, does not modify any data, does not execute code or commands, and does not involve financial transactions. This is a straightforward read operation searching a public database of recreation areas.
From the tool's definition Tool performs a search operation that 'Search[es] federal recreation AREAS...by name, state, or activity.' This is a query/retrieval action with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs recreation_search_recareas 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_recareas, this is the rule to start with:
recreation_search_recareas 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_recareas call is checked against it from then on.
Questions about recreation_search_recareas
Search federal recreation AREAS (broader units: a whole national forest, a national park unit, a BLM management area) by name, state, or activity. For higher-level place search use this; for specific facilities (campgrounds, trailheads) use recreation_search_facilities. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
recreation_search_recareas 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_recareas: 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_recareas 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_recareas 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_recareas. 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_recareas 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