AI agents call cleanup_downloads_tool to permanently remove resources in Geo — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cleaning up files typically means deleting or removing them from storage, which is an irreversible action. Once downloaded GEO dataset files are deleted, they must be re-downloaded. The description is brief but the term 'clean up' in the context of file management strongly implies deletion. Severity is high because it could remove large downloaded datasets that took significant time/resources to acquire.
From the tool's definition 'Clean up downloaded files' — cleanup implies deletion/removal of downloaded data files
Documented attack patterns abuse exactly the kind of access cleanup_downloads_tool 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 cleanup_downloads_tool:
{
"version": "1",
"default": "deny",
"hide": [
"cleanup_downloads_tool"
]
} cleanup_downloads_tool disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Clean up downloaded files. It is categorised as a Destructive tool in the Geo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Geo MCP server in PolicyLayer and add a rule for cleanup_downloads_tool: 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.
cleanup_downloads_tool is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cleanup_downloads_tool 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 cleanup_downloads_tool. 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.
cleanup_downloads_tool 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.