overpass-around-amenity

Find OSM nodes tagged with a given amenity within a radius (m)

SERVERMeta Data Mcp SOURCEpypi:meta-data-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-derekslinz-meta-data-mcp/overpass-around-amenity.md

WHAT IT DOES

What overpass-around-amenity does on Meta Data Mcp

AI agents call overpass-around-amenity to retrieve information from Meta Data 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 overpass-around-amenity is rated Low

This tool performs a geospatial read operation against public OSM data. It retrieves amenity information within a specified geographic radius. There are no side effects, data modifications, code execution, deletions, or financial implications. The worst-case misuse would be mapping sensitive locations (e.g., shelters, medical facilities), but this data is already public and the tool merely queries it.

From the tool's definition Tool queries Open Street Map data to 'Find OSM nodes tagged with a given amenity within a radius' — a retrieval operation with no modification, creation, or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs overpass-around-amenity safely

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

overpass-around-amenity Allowed

overpass-around-amenity 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": {
    "overpass-around-amenity": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Data Mcp, apply this rule, and every overpass-around-amenity call is checked against it from then on.

FAQ

Questions about overpass-around-amenity

What does the overpass-around-amenity tool do? +

Find OSM nodes tagged with a given amenity within a radius (m). It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on overpass-around-amenity? +

Register the Meta Data MCP server in PolicyLayer and add a rule for overpass-around-amenity: 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 Meta Data Mcp. Nothing to install.

What risk level is overpass-around-amenity? +

overpass-around-amenity is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit overpass-around-amenity? +

Yes. Add a rate_limit block to the overpass-around-amenity 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 overpass-around-amenity completely? +

Set action: deny in the PolicyLayer policy for overpass-around-amenity. 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 overpass-around-amenity? +

overpass-around-amenity is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meta Data, and thousands of servers like it.

This server

All 396 Meta Data tools →

Across the catalogue

The MCP Attack Database →

Guides

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