Retrieve collections created by Rijksstudio users. These are curated sets of artworks that users have grouped together based on themes, artists, periods, or personal interests.\n\n
AI agents call get_user_sets to retrieve information from Rijksmuseum MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves user-created collections from the Rijksmuseum database. It performs a data retrieval operation only, returning information about publicly available curated artwork sets. There are no indications of write, destructive, or execution capabilities.
From the tool's definition Tool description states 'Retrieve collections created by Rijksstudio users' - retrieve is a read-only operation with no side effects. No modification, deletion, or execution is indicated.
Documented attack patterns abuse exactly the kind of access get_user_sets gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Rijksmuseum MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_user_sets:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_sets": {}
}
}get_user_sets is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve collections created by Rijksstudio users. These are curated sets of artworks that users have grouped together based on themes, artists, periods, or personal interests.\n\n. It is categorised as a Read tool in the Rijksmuseum MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rijksmuseum MCP Server MCP server in PolicyLayer and add a rule for get_user_sets: 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 Rijksmuseum MCP Server. Nothing to install.
get_user_sets 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 get_user_sets 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 get_user_sets. 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.
get_user_sets is provided by the Rijksmuseum MCP Server MCP server (r-huijts/rijksmuseum-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Rijksmuseum MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 Rijksmuseum MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.