geo.elevation

Ground elevation above sea level (meters + feet) for any coordinate on Earth. Pass lat + lon. ~90m DEM. Source: Open-Meteo (keyless).

SERVERMcp SOURCE@2sio/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/geo.elevation.md

WHAT IT DOES

What geo.elevation does on Mcp

AI agents call geo.elevation to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why geo.elevation is rated Low

This tool queries a public elevation database and returns read-only data based on geographic coordinates. It has no side effects, cannot modify data, execute code, delete information, or commit financial resources. The query-based retrieval of environmental metadata is purely informational.

From the tool's definition Tool description states it 'retrieves...Ground elevation above sea level (meters + feet) for any coordinate on Earth' via 'Open-Meteo (keyless)'. No modification, deletion, execution, or financial transaction is performed.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs geo.elevation safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For geo.elevation, this is the rule to start with:

geo.elevation Allowed

geo.elevation is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "geo.elevation": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every geo.elevation call is checked against it from then on.

FAQ

Questions about geo.elevation

What does the geo.elevation tool do? +

Ground elevation above sea level (meters + feet) for any coordinate on Earth. Pass lat + lon. ~90m DEM. Source: Open-Meteo (keyless). It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on geo.elevation? +

Register the MCP server in PolicyLayer and add a rule for geo.elevation: 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 Mcp. Nothing to install.

What risk level is geo.elevation? +

geo.elevation is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit geo.elevation? +

Yes. Add a rate_limit block to the geo.elevation 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.

How do I block geo.elevation completely? +

Set action: deny in the PolicyLayer policy for geo.elevation. 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.

What MCP server provides geo.elevation? +

geo.elevation is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →