Low Risk

search_by_unit

search_by_unit

How to control search_by_unit ↓

What search_by_unit does on Smithsonian Open Access MCP Server

AI agents call search_by_unit 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.

Low Risk

Why search_by_unit needs a policy

This tool appears to search or filter Smithsonian collection objects by organizational unit. The 'search' prefix, empty (non-destructive) description, and consistent pattern with other Read-category sibling tools indicates data retrieval with no capability to modify, delete, or execute operations. Blast radius if misused is minimal—an AI agent can only retrieve publicly available museum data.

From the tool's definition Tool name 'search_by_unit' combined with server context showing 'search, explore, and analyze' capabilities over collection objects.

Documented attack patterns abuse exactly the kind of access search_by_unit gives an agent:

How to control search_by_unit

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_by_unit:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_by_unit": {}
  }
}

search_by_unit is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Smithsonian Open Access MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_by_unit

What does the search_by_unit tool do? +

search_by_unit. It is categorised as a Read tool in the Smithsonian Open Access MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_by_unit? +

Register the Smithsonian Open Access MCP Server MCP server in PolicyLayer and add a rule for search_by_unit: 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.

What risk level is search_by_unit? +

search_by_unit is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_by_unit? +

Yes. Add a rate_limit block to the search_by_unit 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.

How do I block search_by_unit completely? +

Set action: deny in the PolicyLayer policy for search_by_unit. 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.

What MCP server provides search_by_unit? +

search_by_unit 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.

Enforce policy on every Smithsonian Open Access MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.