met-search-by-artist
Search the Met Museum collection restricted to artist or culture fields.
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/met-search-by-artist.md
What met-search-by-artist does on Meta Data Mcp
AI agents call met-search-by-artist to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why met-search-by-artist is rated Low
This is a straightforward search/query tool against public museum data APIs. It retrieves information without side effects, matching the 'Read' category. The severity is low because museum metadata queries pose minimal risk even if misused—no financial transactions, destructive operations, or code execution are possible. Confidence is high given the clear read-only nature of the operation.
From the tool's definition Tool performs a 'Search' operation on the Met Museum collection, querying by 'artist or culture fields'. The description uses read-only verbs (search, restricted to query fields) with no indication of data modification, deletion, or code execution.
Attacks that exploit this kind of access
The rule that runs met-search-by-artist safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For met-search-by-artist, this is the rule to start with:
met-search-by-artist is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Data Mcp, apply this rule, and every met-search-by-artist call is checked against it from then on.
Questions about met-search-by-artist
Search the Met Museum collection restricted to artist or culture fields. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.
Register the Meta Data MCP server in PolicyLayer and add a rule for met-search-by-artist: 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 Meta Data Mcp. Nothing to install.
met-search-by-artist 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-by-artist 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-by-artist. 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-by-artist is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Data, and thousands of servers like it.
This server
Across the catalogue