Open a high-resolution image of an artwork in the default web browser for viewing. This tool is useful when you want to examine an artwork visually or show it to the user. Works with any valid Rijksmuseum image URL.
AI agents invoke open_image_in_browser to trigger actions in Rijksmuseum MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool actively opens the default web browser on the host system, which is an external side-effecting operation (browser execution). While the intent is benign image viewing, it interacts with the OS environment by launching or directing an application, placing it in the Execute category rather than Read.
From the tool's definition 'Open a high-resolution image of an artwork in the default web browser' — triggers an external operation (launching/controlling the browser)
Documented attack patterns abuse exactly the kind of access open_image_in_browser 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 open_image_in_browser:
{
"version": "1",
"default": "deny",
"tools": {
"open_image_in_browser": {
"limits": [
{
"counter": "open_image_in_browser_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}open_image_in_browser stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Open a high-resolution image of an artwork in the default web browser for viewing. This tool is useful when you want to examine an artwork visually or show it to the user. Works with any valid Rijksmuseum image URL. It is categorised as a Execute tool in the Rijksmuseum MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Rijksmuseum MCP Server MCP server in PolicyLayer and add a rule for open_image_in_browser: 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.
open_image_in_browser is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the open_image_in_browser 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 open_image_in_browser. 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.
open_image_in_browser 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.