Search the Metropolitan Museum of Art collection by keyword and optional filters; returns total match count and a page of object IDs. Always chain the returned IDs to met_get_object (up to 20 at a time) to retrieve full records. Search relevance is keyword-based, not semantic — use concise terms ...
Risk signalsHigh parameter count (10 properties)
Part of the Met Museum Mcp Server server.
Free to start. No card required.
AI agents call met_search to retrieve information from Met Museum 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 met_search 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": {
"met_search": {}
}
}See the full Met Museum Mcp Server policy for all 3 tools.
These attack patterns abuse exactly the kind of access met_search 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.
Search the Metropolitan Museum of Art collection by keyword and optional filters; returns total match count and a page of object IDs. Always chain the returned IDs to met_get_object (up to 20 at a time) to retrieve full records. Search relevance is keyword-based, not semantic — use concise terms and apply departmentId or geoLocation filters to sharpen results. The medium parameter maps to the classification field (pass "Paintings", "Drawings", etc., not material descriptions like "Oil on canvas"). isPublicDomain guarantees CC0-licensed images; hasImages also includes copyrighted works.. It is categorised as a Read tool in the Met Museum Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Met Museum Mcp Server MCP server in PolicyLayer and add a rule for met_search: 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 Met Museum Mcp Server. Nothing to install.
met_search 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 met_search 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 met_search. 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.
met_search is provided by the Met Museum Mcp Server MCP server (@cyanheads/met-museum-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 3 Met Museum 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.