met-get-object
Fetch the full metadata record for a Met Museum object by object ID.
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/met-get-object.md
What met-get-object does on Meta Data Mcp
AI agents call met-get-object 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-get-object is rated Low
This tool retrieves metadata records from the Metropolitan Museum of Art's public API. It performs a query operation that returns data without modifying, creating, deleting, or executing any operations. The action is purely informational and has no blast radius beyond data disclosure.
From the tool's definition Tool name 'met-get-object' and description 'Fetch the full metadata record' indicate a retrieval operation. The verb 'fetch' and context of querying a museum's metadata API confirm read-only data access with no side effects.
Attacks that exploit this kind of access
The rule that runs met-get-object 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-get-object, this is the rule to start with:
met-get-object 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-get-object call is checked against it from then on.
Questions about met-get-object
Fetch the full metadata record for a Met Museum object by object ID. 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-get-object: 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-get-object 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-get-object 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-get-object. 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-get-object 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