media.loc.item
Get full metadata + asset URLs (image, audio, PDF) for a Library of Congress item by its ID or full LOC URL. Includes rights, contributors, subjects, and digitized resource list. LOC public domain
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/media.loc.item.md
What media.loc.item does on Apibase
AI agents call media.loc.item 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 | Library of Congress item ID or full LOC URL (e.g. "item/2003675333" or "https://www.loc.gov/item/2003675333/"). Returns metadata + asset URLs. |
Parameters from the server's own tool schema.
Why media.loc.item is rated Low
Retrieves Library of Congress metadata and URLs; read-only with no side effects or data modification.
From the tool's definition Get full metadata + asset URLs, public domain, no write operations
Attacks that exploit this kind of access
The rule that runs media.loc.item 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 media.loc.item, this is the rule to start with:
media.loc.item 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 media.loc.item call is checked against it from then on.
Questions about media.loc.item
Get full metadata + asset URLs (image, audio, PDF) for a Library of Congress item by its ID or full LOC URL. Includes rights, contributors, subjects, and digitized resource list. LOC public domain. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
media.loc.item 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 media.loc.item: 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.
media.loc.item 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 media.loc.item 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 media.loc.item. 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.
media.loc.item 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