met.collection.departments
List all 19 curatorial departments at The Metropolitan Museum of Art with their IDs and names — American Decorative Arts, Egyptian Art, European Paintings, Greek and Roman Art, Modern Art, and more. Use department IDs with met.browse to explore a collection area or with met.search to filter searc...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/met.collection.departments.md
What met.collection.departments does on Apibase
AI agents call met.collection.departments to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sort_by | string | — | Sort order for the department list: "id" (numeric, default) or "name" (alphabetical) |
Parameters from the server's own tool schema.
Why met.collection.departments is rated Low
Retrieves public metadata about museum departments; no side effects or data modification.
From the tool's definition List all 19 curatorial departments with their IDs and names
Attacks that exploit this kind of access
The rule that runs met.collection.departments safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For met.collection.departments, this is the rule to start with:
met.collection.departments 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 Apibase, apply this rule, and every met.collection.departments call is checked against it from then on.
Questions about met.collection.departments
List all 19 curatorial departments at The Metropolitan Museum of Art with their IDs and names — American Decorative Arts, Egyptian Art, European Paintings, Greek and Roman Art, Modern Art, and more. Use department IDs with met.browse to explore a collection area or with met.search to filter searches. CC0 public domain (Met Museum). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
met.collection.departments accepts 1 parameter: sort_by. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for met.collection.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 Apibase. Nothing to install.
met.collection.departments 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 met.collection.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.
Set action: deny in the PolicyLayer policy for met.collection.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.
met.collection.departments is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue