Low Risk

get_museum_collection_types

get_museum_collection_types

How to control get_museum_collection_types ↓

What get_museum_collection_types does on Smithsonian Open Access MCP Server

AI agents call get_museum_collection_types 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 get_museum_collection_types needs a policy

This tool retrieves or enumerates collection type information from the Smithsonian database with no side effects. It matches the 'Read' category (list, get, fetch operations). Severity is low because the blast radius of misuse is minimal—an agent can only retrieve publicly available museum classification data, not modify, delete, or access restricted resources.

From the tool's definition Tool name 'get_museum_collection_types' indicates retrieval of metadata about available collection types. Sibling tools like 'get_collection_statistics', 'find_on_view_items', and 'get_object_details' all perform read-only queries against the Smithsonian's…

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

How to control get_museum_collection_types

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

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

get_museum_collection_types 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 get_museum_collection_types

What does the get_museum_collection_types tool do? +

get_museum_collection_types. 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 get_museum_collection_types? +

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

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

Can I rate-limit get_museum_collection_types? +

Yes. Add a rate_limit block to the get_museum_collection_types 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 get_museum_collection_types completely? +

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

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