AI agents call get_objects_on_view to retrieve information from Smithsonian Open Access MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about museum objects on display—a read operation with no side effects. No data is created, modified, deleted, or external actions triggered. The blast radius of misuse is minimal; an AI agent could only over-query or retrieve unwanted metadata, which poses negligible risk. Low severity is appropriate for informational access to public museum collections.
From the tool's definition Tool name 'get_objects_on_view' combined with sibling tools like 'find_on_view_items', 'get_museum_highlights_on_view', and server description stating it 'enables finding objects currently on exhibit' and 'retrieving detailed metadata' indicates this…
Documented attack patterns abuse exactly the kind of access get_objects_on_view gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Smithsonian Open Access MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_objects_on_view:
{
"version": "1",
"default": "deny",
"tools": {
"get_objects_on_view": {}
}
}get_objects_on_view 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.
get_objects_on_view. It is categorised as a Read tool in the Smithsonian Open Access MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Smithsonian Open Access MCP Server MCP server in PolicyLayer and add a rule for get_objects_on_view: 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 Smithsonian Open Access MCP Server. Nothing to install.
get_objects_on_view 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_objects_on_view 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_objects_on_view. 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_objects_on_view is provided by the Smithsonian Open Access MCP Server MCP server (molanojustin/smithsonian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Smithsonian Open Access MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
28 Smithsonian Open Access MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.