opendata_regions_list

List the controlled region vocabulary used by the provider registry (e.g.

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/opendata-regions-list.md

WHAT IT DOES

What opendata_regions_list does on Meta Data Mcp

AI agents call opendata_regions_list 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 opendata_regions_list is rated Low

This tool queries and retrieves metadata about region vocabulary from a provider registry. It is a simple data retrieval operation with no ability to modify, delete, or execute external actions. The low severity reflects that exposing region vocabulary lists poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name 'opendata_regions_list' and description 'List the controlled region vocabulary' indicate a read-only retrieval operation. The verb 'list' is explicitly listed in the Read category guidelines.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

opendata_regions_list Allowed

opendata_regions_list 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": {
    "opendata_regions_list": {}
  }
}

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

FAQ

Questions about opendata_regions_list

What does the opendata_regions_list tool do? +

List the controlled region vocabulary used by the provider registry (e.g. 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 opendata_regions_list? +

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

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

Can I rate-limit opendata_regions_list? +

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

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

opendata_regions_list 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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