dpla.archives.detail
Fetch the full metadata record for a specific DPLA item by its 32-character hex identifier. Returns complete fields: title, creator, date, type, format, subject tags, language, rights category, contributing institution, original item URL, and thumbnail URL. Use after a search call to retrieve com...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/dpla.archives.detail.md
What dpla.archives.detail does on Apibase
AI agents call dpla.archives.detail 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 |
|---|---|---|---|
item_id | string | Yes | DPLA item identifier (32-character hex string, e.g. "eb930b2f9ad638f921429e5e898f0a34"). Obtain from search results. |
Parameters from the server's own tool schema.
Why dpla.archives.detail is rated Low
Retrieves metadata for a digitized archive item with no data modification or side effects.
From the tool's definition Fetch the full metadata record for a specific DPLA item
Attacks that exploit this kind of access
The rule that runs dpla.archives.detail 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 dpla.archives.detail, this is the rule to start with:
dpla.archives.detail 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 dpla.archives.detail call is checked against it from then on.
Questions about dpla.archives.detail
Fetch the full metadata record for a specific DPLA item by its 32-character hex identifier. Returns complete fields: title, creator, date, type, format, subject tags, language, rights category, contributing institution, original item URL, and thumbnail URL. Use after a search call to retrieve complete details for a specific digitized object. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
dpla.archives.detail accepts 1 parameter: item_id. Required: item_id. 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 dpla.archives.detail: 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.
dpla.archives.detail 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 dpla.archives.detail 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 dpla.archives.detail. 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.
dpla.archives.detail 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