soil.survey.properties
Get USDA SSURGO soil properties for a US location by lat/lon (WGS84). Returns dominant component(s) with depth-stratified horizons including drainage class, taxonomic class, pH, organic matter %, and sand/silt/clay percentages per horizon. Coverage: US continental + Alaska + Hawaii + territories;...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/soil.survey.properties.md
What soil.survey.properties does on Apibase
AI agents call soil.survey.properties 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 |
|---|---|---|---|
lat | number | Yes | Latitude in WGS84 decimal degrees (e.g. 42.0 for central Iowa farmland, 38.89 for Washington DC). Coverage: US continental + Alaska + Hawaii + territories. |
lon | number | Yes | Longitude in WGS84 decimal degrees (e.g. -93.5 for central Iowa, -77.03 for Washington DC). Note: longitude FIRST in coordinate pairs only matters for SQL — thi |
Parameters from the server's own tool schema.
Why soil.survey.properties is rated Low
Tool retrieves publicly available USDA soil survey data with no side effects or modifications.
From the tool's definition Get USDA SSURGO soil properties, returns dominant component(s) with depth-stratified horizons.
Attacks that exploit this kind of access
The rule that runs soil.survey.properties 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 soil.survey.properties, this is the rule to start with:
soil.survey.properties 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 soil.survey.properties call is checked against it from then on.
Questions about soil.survey.properties
Get USDA SSURGO soil properties for a US location by lat/lon (WGS84). Returns dominant component(s) with depth-stratified horizons including drainage class, taxonomic class, pH, organic matter %, and sand/silt/clay percentages per horizon. Coverage: US continental + Alaska + Hawaii + territories; international/water/unsurveyed points return empty components array. Authoritative source: NRCS Soil Data Access (no auth, unlimited free, US Gov open data). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
soil.survey.properties accepts 2 parameters: lat, lon. Required: lat, 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 soil.survey.properties: 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.
soil.survey.properties 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 soil.survey.properties 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 soil.survey.properties. 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.
soil.survey.properties 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