find_related_collections
AI agents call find_related_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.
Based on the OpenLandMap server's established function (catalog discovery and retrieval) and the pattern of sibling tools that are all Read operations querying environmental datasets, 'find_related_collections' almost certainly retrieves or lists metadata about related geospatial collections without modifying any data. No side effects are expected.
From the tool's definition Tool name 'find_related_collections' suggests discovery/search functionality. The server description establishes that this MCP server's purpose is to 'discover, search, and retrieve' geospatial datasets.
Attacks that exploit this kind of access
find_related_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 find_related_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.
find_related_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 find_related_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 find_related_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.
find_related_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 →