vam.collections.by_maker
Search V&A collection objects created by a specific artist, designer, or maker. Returns objects with maker name, date, object type, place, thumbnail URL, and display status. Supports partial name matching. Examples: "Wedgwood" (1,300+ ceramics), "William Morris" (textiles/designs), "Constable" (p...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/vam.collections.by-maker.md
What vam.collections.by_maker does on Apibase
AI agents call vam.collections.by_maker to retrieve information from Apibase 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 |
|---|---|---|---|
page | integer | — | Page number for pagination (default 1). |
maker | string | Yes | Artist or maker name to search for (e.g. "Wedgwood", "William Morris", "Constable", "Beatrix Potter"). Partial matches are supported. |
page_size | integer | — | Number of results per page (1-30, default 10). |
object_type | string | — | Filter maker results by object type (e.g. "Painting", "Ceramic", "Print"). |
Parameters from the server's own tool schema.
Why vam.collections.by_maker is rated Low
Tool retrieves and queries museum collection data without side effects.
From the tool's definition Search collection objects, returns objects with metadata, no modification.
Attacks that exploit this kind of access
The rule that runs vam.collections.by_maker safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vam.collections.by_maker, this is the rule to start with:
vam.collections.by_maker 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 Apibase, apply this rule, and every vam.collections.by_maker call is checked against it from then on.
Questions about vam.collections.by_maker
Search V&A collection objects created by a specific artist, designer, or maker. Returns objects with maker name, date, object type, place, thumbnail URL, and display status. Supports partial name matching. Examples: "Wedgwood" (1,300+ ceramics), "William Morris" (textiles/designs), "Constable" (paintings), "Beatrix Potter" (drawings). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
vam.collections.by_maker accepts 4 parameters: page, maker, page_size, object_type. Required: maker. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for vam.collections.by_maker: 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 Apibase. Nothing to install.
vam.collections.by_maker 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 vam.collections.by_maker 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 vam.collections.by_maker. 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.
vam.collections.by_maker is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue