// MCP TOOL REFERENCE

RIJKSMUSEUM MCP+ TOOLS

24 tools from the Rijksmuseum Mcp+ MCP Server, categorised by risk level.

// ALL 24 RIJKSMUSEUM MCP+ TOOLS

READ 13 tools

Read navigate_viewer Use after inspect_artwork_image when you want to draw the user Read browse_set Use when you have a setSpec (from list_curated_sets) and want to enumerate its member artworks. Read collection_stats Aggregate counts, percentages, distributions, histograms, totals, summaries, and group-by / count-by / dist... Read find_similar Use when the user has a SPECIFIC artwork (objectNumber) and wants others like it. Read get_artwork_details Use when you need full metadata for a SINGLE artwork (e.g. after a search_artwork / semantic_search / find_... Read get_recent_changes Use when you need OAI-PMH delta semantics specifically — tracking what changed since a known harvest checkp... Read inspect_artwork_image Use when YOU (the LLM) need to look at an artwork image or region for visual analysis — identifying details... Read list_curated_sets Use when you want to discover curated collection sets (193 total) ranging from substantive sub-collections Read search_artwork Use when you have specific filter criteria (subject, material, technique, dates, place, person, theme, …) a... Read search_inscriptions Structured search over artwork inscriptions — collector Read search_persons Use when the user has a demographic or structural query about persons (artists, depicted figures, donors): Read search_provenance Use when the user has a provenance question — ownership history, collectors, sales, inheritances, gifts, co... Read semantic_search Use when the user has a free-text concept (

WRITE 11 tools

Write report_audit_findings Report audit findings comparing parser output against raw provenance text Write report_event_reclassification Report events that should be reclassified as non-provenance or merged with adjacent events Write report_event_splits Report events that should be split into multiple atomic provenance events Write report_field_corrections Report field-level corrections for provenance events with wrong/truncated location or missing receiver parties Write report_party_disambiguation Report the correct party decomposition for a merged/artifact party name Write report_party_extraction Extract parties (sender, receiver, agent) from provenance events where the parser found no parties Write report_pattern_findings Report pattern analysis for unknown provenance segments Write report_position_enrichment Report inferred party positions and transfer categories for ambiguous provenance events Write report_semantic_findings Report from-scratch provenance parsing with reasoning type classification Write report_structural_signals Report structural signals found in unknown provenance segments that could enable deterministic classification Write report_type_classification Classify transfer types for individual unknown provenance events that no parser rule can handle

// FAQ

How many tools does the Rijksmuseum Mcp+ MCP server have? +

The Rijksmuseum Mcp+ MCP server exposes 24 tools across 2 categories: Read, Write.

How do I enforce policies on Rijksmuseum Mcp+ tools? +

Route the Rijksmuseum Mcp+ server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Rijksmuseum Mcp+ tools fall into? +

Rijksmuseum Mcp+ tools are categorised as Read (13), Write (11). Each category has a recommended default policy.

Enforce policy on every Rijksmuseum Mcp+ tool call.

Start from Rijksmuseum Mcp+, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.