AI agents call get_smithsonian_units 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 Smithsonian organizational units or metadata—a query operation with no side effects, data modification, or external triggering. It fits the Read category as a lookup/fetch function. Severity is low because retrieving publicly-available museum information poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_smithsonian_units' indicates data retrieval. Context shows this server provides read-only access to Smithsonian collection metadata and search capabilities. Sibling tools are all read operations (check, find, get, continue_explore).
Documented attack patterns abuse exactly the kind of access get_smithsonian_units 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_smithsonian_units:
{
"version": "1",
"default": "deny",
"tools": {
"get_smithsonian_units": {}
}
}get_smithsonian_units 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_smithsonian_units. 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_smithsonian_units: 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_smithsonian_units 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_smithsonian_units 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_smithsonian_units. 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_smithsonian_units 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.