get_soil_collections
AI agents call get_soil_collections to retrieve information from OpenLandMap MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or lists soil-related collections from the OpenLandMap STAC catalog. It is a query/discovery operation with no side effects, no data modification, and no destructive actions. While the description is empty, the context from sibling tools and the server's stated purpose (to enable discovery and retrieval of datasets) clearly indicates read-only behavior.
From the tool's definition Tool name 'get_soil_collections' combined with sibling tools like 'discover_data_for_topic', 'find_collections_for_bbox', 'find_items_by_point', and 'get_all_data_assets' all indicate data retrieval operations.
Attacks that exploit this kind of access
get_soil_collections. It is categorised as a Read tool in the OpenLandMap MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenLandMap MCP Server MCP server in PolicyLayer and add a rule for get_soil_collections: 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 OpenLandMap MCP Server. Nothing to install.
get_soil_collections 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 get_soil_collections 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 get_soil_collections. 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.
get_soil_collections is provided by the OpenLandMap MCP Server MCP server (tharlestsa/openlandmap_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →