met-list-departments

List the curatorial departments at the Met Museum.

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/met-list-departments.md

WHAT IT DOES

What met-list-departments does on Meta Data Mcp

AI agents call met-list-departments 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 met-list-departments is rated Low

This tool queries and returns information about Met Museum departments. It performs a simple data retrieval operation analogous to a GET request or database SELECT. There is no modification, deletion, execution of code, or financial impact. The blast radius of misuse is minimal — an agent could only retrieve already-public museum organizational data.

From the tool's definition 'List the curatorial departments' — a direct retrieval/listing operation with no side effects or data modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

met-list-departments Allowed

met-list-departments 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": {
    "met-list-departments": {}
  }
}

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

FAQ

Questions about met-list-departments

What does the met-list-departments tool do? +

List the curatorial departments at the Met Museum. 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 met-list-departments? +

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

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

Can I rate-limit met-list-departments? +

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

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

met-list-departments 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 →