Download GEO data files (SOFT format)
AI agents use download_geo_data to create or update resources in Geo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Geo environment.
This tool downloads files from an external source (NCBI GEO) and writes them to the local filesystem. It creates new files locally, which is a Write operation. It does not delete data, execute code, or move money. Severity is medium because it can consume disk space and download potentially large datasets, but the blast radius is limited to local storage.
From the tool's definition Download GEO data files (SOFT format)
Documented attack patterns abuse exactly the kind of access download_geo_data 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 download_geo_data:
{
"version": "1",
"default": "deny",
"tools": {
"download_geo_data": {
"limits": [
{
"counter": "download_geo_data_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} download_geo_data stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Download GEO data files (SOFT format). It is categorised as a Write tool in the Geo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Geo MCP server in PolicyLayer and add a rule for download_geo_data: 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.
download_geo_data is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the download_geo_data 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 download_geo_data. 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.
download_geo_data 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.