met.collection.browse
Browse all artworks in a Met Museum department by department ID, with pagination. Returns a page of object IDs — use met.details to fetch full artwork metadata for each ID. Use met.departments to get department IDs (e.g. 10=Egyptian Art, 11=European Paintings, 21=Modern Art). CC0 public domain (M...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/met.collection.browse.md
What met.collection.browse does on Apibase
AI agents call met.collection.browse 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 |
|---|---|---|---|
page | integer | — | Page number for pagination (1-based, default 1). Each page returns up to 100 object IDs. |
per_page | integer | — | Number of object IDs per page (1–100, default 50). Use with met.details to fetch artwork metadata. |
department_id | integer | Yes | Department ID to browse. Use met.departments to get IDs. Examples: 10=Egyptian Art, 11=European Paintings, 13=Greek and Roman Art, 21=Modern Art |
Parameters from the server's own tool schema.
Why met.collection.browse is rated Low
Retrieves public domain artwork metadata with no ability to modify, delete, or execute operations.
From the tool's definition Browse all artworks, Returns a page of object IDs, pagination, fetch metadata
Attacks that exploit this kind of access
The rule that runs met.collection.browse 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.browse, this is the rule to start with:
met.collection.browse 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.browse call is checked against it from then on.
Questions about met.collection.browse
Browse all artworks in a Met Museum department by department ID, with pagination. Returns a page of object IDs — use met.details to fetch full artwork metadata for each ID. Use met.departments to get department IDs (e.g. 10=Egyptian Art, 11=European Paintings, 21=Modern Art). 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.browse accepts 3 parameters: page, per_page, department_id. Required: department_id. 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.browse: 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.browse 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.browse 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.browse. 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.browse 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