travel.nps.campgrounds
NPS campgrounds with reservation info, accessibility, amenities, coords. NPS public domain
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/travel.nps.campgrounds.md
What travel.nps.campgrounds does on Apibase
AI agents call travel.nps.campgrounds to retrieve information from Apibase 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 |
|---|---|---|---|
q | string | — | Free-text keyword search. |
limit | integer | — | Max records to return (default 10, max 50). |
start | integer | — | Pagination offset for stepping through results. |
park_code | string | — | Optional park code (e.g. "yose" Yosemite, "yell" Yellowstone, "grca" Grand Canyon). Comma-separated allowed. |
state_code | string | — | Optional 2-letter US state code (e.g. "CA", "NY", "WY"). Comma-separated for multiple ("CA,WY"). |
Parameters from the server's own tool schema.
Why travel.nps.campgrounds is rated Low
Retrieves public campground data; no creation, modification, or deletion capability.
From the tool's definition NPS campgrounds with reservation info, accessibility, amenities, coords
Attacks that exploit this kind of access
The rule that runs travel.nps.campgrounds safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For travel.nps.campgrounds, this is the rule to start with:
travel.nps.campgrounds 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 Apibase, apply this rule, and every travel.nps.campgrounds call is checked against it from then on.
Questions about travel.nps.campgrounds
NPS campgrounds with reservation info, accessibility, amenities, coords. NPS public domain. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
travel.nps.campgrounds accepts 5 parameters: q, limit, start, park_code, state_code. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for travel.nps.campgrounds: 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 Apibase. Nothing to install.
travel.nps.campgrounds 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 travel.nps.campgrounds 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 travel.nps.campgrounds. 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.
travel.nps.campgrounds is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue