Discover objects across Smithsonian collections related to a given anchor object. Fetches the anchor object's metadata (culture, period, object type, maker names, topic terms), then fans out up to 4 parallel searches using different metadata signals as queries. Deduplicates against the anchor and...
Part of the Smithsonian Mcp Server server.
Free to start. No card required.
AI agents call smithsonian_find_related to retrieve information from Smithsonian Mcp Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though smithsonian_find_related only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"smithsonian_find_related": {}
}
}See the full Smithsonian Mcp Server policy for all 6 tools.
These attack patterns abuse exactly the kind of access smithsonian_find_related gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Discover objects across Smithsonian collections related to a given anchor object. Fetches the anchor object's metadata (culture, period, object type, maker names, topic terms), then fans out up to 4 parallel searches using different metadata signals as queries. Deduplicates against the anchor and merges results into a ranked list. Cross-museum discovery is the differentiator — an NASM aerospace anchor may surface related objects from NMNH, SAAM, and NMAH.. It is categorised as a Read tool in the Smithsonian Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Smithsonian Mcp Server MCP server in PolicyLayer and add a rule for smithsonian_find_related: 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 Mcp Server. Nothing to install.
smithsonian_find_related 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 smithsonian_find_related 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 smithsonian_find_related. 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.
smithsonian_find_related is provided by the Smithsonian Mcp Server MCP server (@cyanheads/smithsonian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Smithsonian Mcp Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.