overpass-query

Execute a raw OverpassQL query against the Overpass API.

SERVERMeta Data Mcp SOURCEpypi:meta-data-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/overpass-query.md

WHAT IT DOES

What overpass-query does on Meta Data Mcp

AI agents invoke overpass-query to trigger actions in Meta Data Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why overpass-query is rated High

The tool executes arbitrary raw OverpassQL queries against an external API. While Overpass API is read-only (it queries OpenStreetMap data), the word 'Execute' and 'raw query' indicate it runs user-supplied code/queries against an external system.

From the tool's definition "Execute a raw OverpassQL query against the Overpass API"

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs overpass-query 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-query, this is the rule to start with:

overpass-query Rate-limited

overpass-query stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "overpass-query": {
      "limits": [
        {
          "counter": "overpass-query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT 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-query call is checked against it from then on.

FAQ

Questions about overpass-query

What does the overpass-query tool do? +

Execute a raw OverpassQL query against the Overpass API. It is categorised as a Execute tool in the Meta Data Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on overpass-query? +

Register the Meta Data MCP server in PolicyLayer and add a rule for overpass-query: 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-query? +

overpass-query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit overpass-query? +

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

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

overpass-query 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 → High-risk tools on this server →

Across the catalogue

aroflo_query_zone on AroFlo MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →