met_departments
List all departments in the Metropolitan Museum of Art.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/met-departments.md
What met_departments does on UnClick
AI agents call met_departments 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.
Why met_departments is rated Low
This tool queries and returns public information about Metropolitan Museum of Art departments. It performs a simple list/fetch operation with no capability to modify, delete, or execute actions. The data retrieved is informational and publicly available, presenting minimal security risk even if misused by an AI agent.
From the tool's definition Tool name 'met_departments' and description 'List all departments' indicate a data retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs met_departments 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_departments, this is the rule to start with:
met_departments 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 UnClick, apply this rule, and every met_departments call is checked against it from then on.
Questions about met_departments
List all departments in the Metropolitan Museum of Art. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
Register the UnClick MCP server in PolicyLayer and add a rule for met_departments: 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.
met_departments 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_departments 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_departments. 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_departments 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue