AI agents call search_and_get_details 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.
The tool queries the Smithsonian's 3 million object collection database to search and retrieve object details, metadata, and related information. This is purely informational access with no side effects. While the description is empty, the name and server context (search, explore, analyze collections) strongly indicate read-only data retrieval.
From the tool's definition Tool name 'search_and_get_details' indicates retrieval operations. Sibling tools include 'search', 'find', 'get_collection_statistics', 'get_object_details', 'get_object_context' — all Read operations querying museum collection metadata.
Documented attack patterns abuse exactly the kind of access search_and_get_details 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 search_and_get_details:
{
"version": "1",
"default": "deny",
"tools": {
"search_and_get_details": {}
}
}search_and_get_details 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.
search_and_get_details. 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 search_and_get_details: 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.
search_and_get_details 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 search_and_get_details 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 search_and_get_details. 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.
search_and_get_details 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.