AI agents call get_on_view_context 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 contextual information about items currently on exhibit in Smithsonian museums. It has no side effects, does not modify data, execute code, delete content, or involve financial transactions. It is a read-only query operation with minimal blast radius if misused—worst case would be excessive API calls or information disclosure of publicly available museum data.
From the tool's definition Tool name 'get_on_view_context' and sibling tools (get_object_details, get_object_context, get_museum_highlights_on_view, find_on_view_items) all indicate data retrieval operations.
Documented attack patterns abuse exactly the kind of access get_on_view_context 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_on_view_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_on_view_context": {}
}
}get_on_view_context 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_on_view_context. 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_on_view_context: 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_on_view_context 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_on_view_context 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_on_view_context. 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_on_view_context 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.