met_object

Get full details for a Met Museum artwork by object ID.

SERVERUnClick SOURCE@unclick/mcp-server

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/met-object.md

WHAT IT DOES

What met_object does on UnClick

AI agents call met_object to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`objectID`	number	Yes	Met Museum object ID

Parameters from the server's own tool schema.

RISK

Why met_object is rated Low

The tool queries the Met Museum's public API to fetch artwork metadata. It retrieves read-only information and has no side effects on data, making it a Read category risk with low severity. The blast radius of misuse is minimal—an agent could only retrieve excessive or unexpected artwork records, which poses no financial, destructive, or operational harm.

From the tool's definition Tool description states 'Get full details for a Met Museum artwork by object ID' — a pure retrieval operation with no modification, deletion, or execution capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs met_object safely

PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For met_object, this is the rule to start with:

met_object Allowed

met_object is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "met_object": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every met_object call is checked against it from then on.

FAQ

Questions about met_object

What does the met_object tool do? +

Get full details for a Met Museum artwork by object ID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.

What parameters does met_object accept? +

met_object accepts 1 parameter: objectID. Required: objectID. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on met_object? +

Register the UnClick MCP server in PolicyLayer and add a rule for met_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 UnClick. Nothing to install.

What risk level is met_object? +

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

Can I rate-limit met_object? +

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

How do I block met_object completely? +

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

What MCP server provides met_object? +

met_object is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →