Get the full record for a single V&A object by its system number (e.g. "O72610", as returned by search_objects). Returns title, maker, object type, materials, description, date, place, dimensions, and a usable image URL. Keyless.
AI agents call get_object to retrieve information from Mcp Va Museum without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | V&A system number, e.g. "O72610". |
Parameters from the server's own tool schema.
This tool only retrieves and returns structured data about museum objects. It performs a read-only query operation with no ability to modify, delete, or execute code. The blast radius of misuse is minimal—an AI agent could only retrieve unwanted public museum data, which poses no security or operational risk.
From the tool's definition Tool description states it 'Get[s] the full record for a single V&A object' and 'Returns title, maker, object type, materials, description, date, dimensions, and a usable image URL.' The action is purely retrieval of museum collection metadata with no…
Attacks that exploit this kind of access
Get the full record for a single V&A object by its system number (e.g. "O72610", as returned by search_objects). Returns title, maker, object type, materials, description, date, place, dimensions, and a usable image URL. Keyless. It is categorised as a Read tool in the Mcp Va Museum MCP Server, which means it retrieves data without modifying state.
get_object accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Va Museum MCP server in PolicyLayer and add a rule for 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 Mcp Va Museum. Nothing to install.
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 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 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.
get_object is provided by the Mcp Va Museum MCP server (pipeworx-io/mcp-va-museum). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →