media.loc.search
Search 415K+ digitized historical items at LOC (photos, manuscripts, maps, newspapers, films, rare books). Filter by online format (image/audio/video/text/web archive) or collection slug. Public domain by US statute (17 USC §105)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/media.loc.search.md
What media.loc.search does on Apibase
AI agents call media.loc.search 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 (1-based). |
limit | integer | — | Results per page (default 20, max 50). |
query | string | Yes | Free-text search across LOC's 415K+ digitized items (e.g. "civil war", "suffrage", "lincoln"). |
format | string | — | Optional filter by online format — image, audio, film/video, online text, or web archive. |
collection | string | — | Optional collection slug to scope the search (e.g. "rosa-parks-papers"). |
Parameters from the server's own tool schema.
Why media.loc.search is rated Low
Retrieves publicly available archival metadata and content without side effects or restrictions.
From the tool's definition Search digitized historical items at LOC, public domain by US statute
Attacks that exploit this kind of access
The rule that runs media.loc.search 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.search, this is the rule to start with:
media.loc.search 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.search call is checked against it from then on.
Questions about media.loc.search
Search 415K+ digitized historical items at LOC (photos, manuscripts, maps, newspapers, films, rare books). Filter by online format (image/audio/video/text/web archive) or collection slug. Public domain by US statute (17 USC §105). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
media.loc.search accepts 5 parameters: page, limit, query, format, collection. Required: query. 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.search: 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.search 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.search 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.search. 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.search 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