rijks.art.search
Search 800,000+ artworks at the Rijksmuseum (Dutch national museum) by title, description, creation date, or object number. Returns Linked Open Data object IDs — use rijks.details for full metadata. Covers Rembrandt, Vermeer, Van Gogh, and centuries of Dutch art. CC-BY license (Rijksmuseum)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/rijks.art.search.md
What rijks.art.search does on Apibase
AI agents call rijks.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 |
|---|---|---|---|
title | string | — | Artwork title search (e.g. "Night Watch", "Self-portrait", "Milkmaid") |
description | string | — | Search within artwork descriptions (e.g. "portrait", "landscape") |
creation_date | string | — | Filter by creation year or date (e.g. "1642", "1665") |
object_number | string | — | Rijksmuseum object number (e.g. "SK-C-5" for Night Watch) |
Parameters from the server's own tool schema.
Why rijks.art.search is rated Low
Tool retrieves and queries museum artwork data without modifying, deleting, or executing operations.
From the tool's definition Search 800,000+ artworks by title, description, creation date, object number. Returns object IDs.
Attacks that exploit this kind of access
The rule that runs rijks.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 rijks.art.search, this is the rule to start with:
rijks.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 rijks.art.search call is checked against it from then on.
Questions about rijks.art.search
Search 800,000+ artworks at the Rijksmuseum (Dutch national museum) by title, description, creation date, or object number. Returns Linked Open Data object IDs — use rijks.details for full metadata. Covers Rembrandt, Vermeer, Van Gogh, and centuries of Dutch art. CC-BY license (Rijksmuseum). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
rijks.art.search accepts 4 parameters: title, description, creation_date, object_number. 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 rijks.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.
rijks.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 rijks.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 rijks.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.
rijks.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