unesco-heritage-search
Search UNESCO World Heritage Sites by name or keyword.
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/unesco-heritage-search.md
What unesco-heritage-search does on Meta Data Mcp
AI agents call unesco-heritage-search 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.
Why unesco-heritage-search is rated Low
This tool retrieves and queries open UNESCO data with no side effects. It is purely informational—searching for heritage sites by name or keyword returns results but does not alter any data. Classification as Read is appropriate with low severity since misuse would only result in excessive queries or information disclosure, posing minimal risk.
From the tool's definition Tool performs a 'search' operation on UNESCO World Heritage Sites by name or keyword. The description explicitly states it 'searches' data without modifying, creating, or deleting records.
Attacks that exploit this kind of access
The rule that runs unesco-heritage-search 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-search, this is the rule to start with:
unesco-heritage-search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Data Mcp, apply this rule, and every unesco-heritage-search call is checked against it from then on.
Questions about unesco-heritage-search
Search UNESCO World Heritage Sites by name or keyword. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.
Register the Meta Data MCP server in PolicyLayer and add a rule for unesco-heritage-search: 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.
unesco-heritage-search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the unesco-heritage-search 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.
Set action: deny in the PolicyLayer policy for unesco-heritage-search. 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.
unesco-heritage-search 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.
More on Meta Data, and thousands of servers like it.
This server
Across the catalogue