unesco-heritage-list-sites

List UNESCO World Heritage Sites, optionally filtered by region, country,

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/unesco-heritage-list-sites.md

WHAT IT DOES

What unesco-heritage-list-sites does on Meta Data Mcp

AI agents call unesco-heritage-list-sites 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 unesco-heritage-list-sites is rated Low

This tool retrieves and queries data from an open UNESCO API with no side effects. It matches the Read category profile: search/list/get/fetch operations that do not modify state or trigger external actions.

From the tool's definition Tool name contains 'list' and description states 'List UNESCO World Heritage Sites' with optional filtering. No modification, deletion, or execution of external operations—purely a data retrieval operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

unesco-heritage-list-sites Allowed

unesco-heritage-list-sites 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": {
    "unesco-heritage-list-sites": {}
  }
}

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 unesco-heritage-list-sites call is checked against it from then on.

FAQ

Questions about unesco-heritage-list-sites

What does the unesco-heritage-list-sites tool do? +

List UNESCO World Heritage Sites, optionally filtered by region, country,. 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 unesco-heritage-list-sites? +

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

unesco-heritage-list-sites is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit unesco-heritage-list-sites? +

Yes. Add a rate_limit block to the unesco-heritage-list-sites 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 unesco-heritage-list-sites completely? +

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

unesco-heritage-list-sites 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 →