opentopo.catalog.lidar
Search the OpenTopography catalog for high-resolution LiDAR point cloud datasets covering a specified bounding box. LiDAR datasets provide centimetre-to-metre resolution 3D terrain data, primarily from USGS 3DEP surveys across the US. Returns dataset name, OpenTopography ID, DOI URL, acquisition ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/opentopo.catalog.lidar.md
What opentopo.catalog.lidar does on Apibase
AI agents call opentopo.catalog.lidar 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 |
|---|---|---|---|
max_lat | number | Yes | Northern boundary of search area in decimal degrees (-90 to 90) |
max_lon | number | Yes | Eastern boundary of search area in decimal degrees (-180 to 180) |
min_lat | number | Yes | Southern boundary of search area in decimal degrees (-90 to 90) |
min_lon | number | Yes | Western boundary of search area in decimal degrees (-180 to 180) |
Parameters from the server's own tool schema.
Why opentopo.catalog.lidar is rated Low
Tool queries and returns metadata about LiDAR datasets without modifying data or executing external operations.
From the tool's definition Search the OpenTopography catalog for high-resolution LiDAR point cloud datasets
Attacks that exploit this kind of access
The rule that runs opentopo.catalog.lidar 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 opentopo.catalog.lidar, this is the rule to start with:
opentopo.catalog.lidar 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 opentopo.catalog.lidar call is checked against it from then on.
Questions about opentopo.catalog.lidar
Search the OpenTopography catalog for high-resolution LiDAR point cloud datasets covering a specified bounding box. LiDAR datasets provide centimetre-to-metre resolution 3D terrain data, primarily from USGS 3DEP surveys across the US. Returns dataset name, OpenTopography ID, DOI URL, acquisition date, spatial coverage bounds, and description. Essential for discovering available high-resolution terrain data before requesting downloads. Source: OpenTopography catalog, CC BY 4.0, free registration (5K req/day). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
opentopo.catalog.lidar accepts 4 parameters: max_lat, max_lon, min_lat, min_lon. Required: max_lat, max_lon, min_lat, min_lon. 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 opentopo.catalog.lidar: 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.
opentopo.catalog.lidar 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 opentopo.catalog.lidar 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 opentopo.catalog.lidar. 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.
opentopo.catalog.lidar 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