usgs-epqs.elevation.point
Get ground surface elevation for a single latitude/longitude coordinate from the USGS 3D Elevation Program (3DEP) — the authoritative US Government digital elevation model, with resolution as fine as 1 meter in many areas. Returns elevation in meters or feet, the source raster resolution, and opt...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/usgs-epqs.elevation.point.md
What usgs-epqs.elevation.point does on Apibase
AI agents call usgs-epqs.elevation.point 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 |
|---|---|---|---|
units | string | — | Elevation output units, "Meters" or "Feet" (default "Meters"). |
latitude | number | Yes | Latitude in decimal degrees, WGS84 (e.g. 39.7147). Continental US + territories only. |
longitude | number | Yes | Longitude in decimal degrees, WGS84 (e.g. -105.0178). |
include_date | boolean | — | Include the source DEM raster acquisition date in the response (default false). |
Parameters from the server's own tool schema.
Why usgs-epqs.elevation.point is rated Low
Retrieves public elevation data from USGS without modifying any resources or executing arbitrary operations.
From the tool's definition Get ground surface elevation for a single latitude/longitude coordinate
Attacks that exploit this kind of access
The rule that runs usgs-epqs.elevation.point 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 usgs-epqs.elevation.point, this is the rule to start with:
usgs-epqs.elevation.point 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 usgs-epqs.elevation.point call is checked against it from then on.
Questions about usgs-epqs.elevation.point
Get ground surface elevation for a single latitude/longitude coordinate from the USGS 3D Elevation Program (3DEP) — the authoritative US Government digital elevation model, with resolution as fine as 1 meter in many areas. Returns elevation in meters or feet, the source raster resolution, and optionally the DEM acquisition date. Continental US + territories only (no ocean or international coverage). Data: epqs.nationalmap.gov (USGS 3D Elevation Program), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
usgs-epqs.elevation.point accepts 4 parameters: units, latitude, longitude, include_date. Required: latitude, longitude. 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 usgs-epqs.elevation.point: 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.
usgs-epqs.elevation.point 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 usgs-epqs.elevation.point 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 usgs-epqs.elevation.point. 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.
usgs-epqs.elevation.point 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