list_datasets
List all available elevation datasets on the Geospatial System server.
This record as markdown: /tools/com-geospatialsystem-location-profile/list-datasets.md
What list_datasets does on Geospatial System — Location Profile
AI agents call list_datasets to retrieve information from Geospatial System — Location Profile without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_datasets is rated Low
This tool retrieves metadata about available datasets without creating, modifying, deleting, or executing any operations. It is a straightforward informational query operation, making it a Read category risk with low severity—minimal blast radius if an AI agent calls it, as it only enumerates existing resources without changing any state.
From the tool's definition Tool name 'list_datasets' and description 'List all available elevation datasets' indicate a query/listing operation with no side effects or modifications.
Attacks that exploit this kind of access
The rule that runs list_datasets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Geospatial System — Location Profile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_datasets, this is the rule to start with:
list_datasets 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 Geospatial System — Location Profile, apply this rule, and every list_datasets call is checked against it from then on.
Questions about list_datasets
List all available elevation datasets on the Geospatial System server. It is categorised as a Read tool in the Geospatial System — Location Profile MCP Server, which means it retrieves data without modifying state.
Register the Geospatial System — Location Profile MCP server in PolicyLayer and add a rule for list_datasets: 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 Geospatial System — Location Profile. Nothing to install.
list_datasets 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 list_datasets 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 list_datasets. 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.
list_datasets is provided by the Geospatial System — Location Profile MCP server (https://api.geospatialsystem.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Geospatial System — Location Profile, and thousands of servers like it.
Across the catalogue