// SCAN REPORT

Geo

11 tools. 2 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 12 Jun 2026

2 can modify or destroy data

9 read-only

11 tools total

Community server · catalogue entry verified 12/06/2026

How to control Geo ↓

TOOL MAP

What Geo exposes to your agents

Read (9) Write / Execute (1) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Geo tools

Destructive · High cleanup_downloads_tool Cleaning up files typically means deleting or removing them from storage, which is an irreversible action. Write · Medium download_geo_data This tool downloads files from an external source (NCBI GEO) and writes them to the local filesystem.

2 of Geo's 11 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Geo

PolicyLayer is an MCP gateway — it sits between your AI agents and Geo, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "cleanup_downloads_tool": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "download_geo_data": {
    "limits": [
      {
        "counter": "download_geo_data_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_download_stats": {
    "limits": [
      {
        "counter": "get_download_stats_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Geo — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON GEO →

Free to start. No card required.

FULL CATALOGUE

All 11 Geo tools

DESTRUCTIVE 1 tools

Destructive cleanup_downloads_tool Clean up downloaded files

WRITE 1 tools

Write download_geo_data Download GEO data files (SOFT format)

READ 9 tools

Read get_download_stats Get download statistics and limits Read get_download_status Check if a GEO dataset has been downloaded Read list_downloaded_datasets List all downloaded GEO datasets Read search_geo Search GEO for all types of records (GSE, GSM, GPL, GDS) Read search_geo_datasets Search GEO Datasets (GDS) - curated gene expression datasets Read search_geo_platforms Search GEO Platforms (GPL) - array/sequencing platforms Read search_geo_profiles Search GEO Profiles database for gene expression profiles Read search_geo_samples Search GEO Samples (GSM) - individual samples Read search_geo_series Search GEO Series (GSE) - complete experiments

FAQ

Questions about Geo

Can an AI agent delete data through the Geo MCP server? +

Yes. The Geo server exposes 1 destructive tools including cleanup_downloads_tool. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Geo? +

The Geo server has 1 write tools including download_geo_data. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Geo.

How many tools does the Geo MCP server expose? +

11 tools across 1 categories: Read. 9 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Geo? +

Register the Geo MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Geo tool call.

Deterministic rules across all 11 Geo tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GEO →

Free to start. No card required.

11 Geo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.