Check if a GEO dataset has been downloaded
AI agents call get_download_status to retrieve information from Geo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only check of download status. It queries existing state (whether a dataset download has completed) with no side effects, no data creation or modification, no code execution, and no destructive actions. It is clearly informational in nature, fitting the Read category.
From the tool's definition Tool description explicitly states 'Check if a GEO dataset has been downloaded' — a query operation that retrieves status information without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access get_download_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Geo, and nothing reaches the server without passing your rules. This is the rule we recommend for get_download_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_download_status": {}
}
}get_download_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if a GEO dataset has been downloaded. It is categorised as a Read tool in the Geo MCP Server, which means it retrieves data without modifying state.
Register the Geo MCP server in PolicyLayer and add a rule for get_download_status: 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 Geo. Nothing to install.
get_download_status 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_download_status 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_download_status. 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_download_status is provided by the Geo MCP server (mcpmed/geomcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Geo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Geo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.