Search GEO for all types of records (GSE, GSM, GPL, GDS)
AI agents call search_geo 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 queries a public bioinformatics database (Gene Expression Omnibus) to retrieve metadata about genomic datasets. It retrieves information without side effects. The low severity reflects that misuse would only expose publicly-available scientific data, with no capability to alter records, execute code, or affect financial or destructive operations.
From the tool's definition Tool is named 'search_geo' and described as 'Search GEO for all types of records'. The verb 'search' is a classic read operation that retrieves data without modification.
Documented attack patterns abuse exactly the kind of access search_geo 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 search_geo:
{
"version": "1",
"default": "deny",
"tools": {
"search_geo": {}
}
}search_geo 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.
Search GEO for all types of records (GSE, GSM, GPL, GDS). 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 search_geo: 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.
search_geo 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 search_geo 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 search_geo. 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.
search_geo 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.