met.art.search
Search 470,000+ artworks at The Metropolitan Museum of Art by keyword, artist, medium, department, date range, or geography. Returns object IDs — use met.details for full metadata and images. CC0 public domain (Met Museum)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/met.art.search.md
What met.art.search does on Apibase
AI agents call met.art.search 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 |
|---|---|---|---|
query | string | Yes | Search keyword — artist, title, medium, or subject (e.g. "monet", "sunflowers", "greek vase", "armor") |
medium | string | — | Medium filter (e.g. "Paintings", "Sculpture", "Photographs", "Ceramics") |
date_end | integer | — | End year for date range filter (e.g. 1900). Use with date_begin. |
date_begin | integer | — | Start year for date range filter (e.g. 1800). Use with date_end. |
has_images | boolean | — | Only return artworks with images (default: true) |
geo_location | string | — | Geographic location filter (e.g. "France", "Japan", "Egypt") |
department_id | integer | — | Department filter: 1=American Decorative Arts, 3=Ancient Near Eastern Art, 6=Asian Art, 9=Drawings and Prints, 11=European Paintings, 13=Greek and Roman Art, 17 |
Parameters from the server's own tool schema.
Why met.art.search is rated Low
Retrieves metadata from public museum collection; no data modification, deletion, or side effects.
From the tool's definition Search...artworks...by keyword, artist, medium. Returns object IDs.
Attacks that exploit this kind of access
The rule that runs met.art.search 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.art.search, this is the rule to start with:
met.art.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 Apibase, apply this rule, and every met.art.search call is checked against it from then on.
Questions about met.art.search
Search 470,000+ artworks at The Metropolitan Museum of Art by keyword, artist, medium, department, date range, or geography. Returns object IDs — use met.details for full metadata and images. 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.art.search accepts 7 parameters: query, medium, date_end, date_begin, has_images, geo_location, department_id. Required: query. 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.art.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 Apibase. Nothing to install.
met.art.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 met.art.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 met.art.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.
met.art.search 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