media.loc.collections
Browse Library of Congress digital collections — Civil War Photographs, Geography & Map Division, Rosa Parks Papers, etc. Returns collection slugs needed for filtered search. LOC public domain
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/media.loc.collections.md
What media.loc.collections does on Apibase
AI agents call media.loc.collections 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 |
|---|---|---|---|
limit | integer | — | Max collections to return (default 20, max 50). |
Parameters from the server's own tool schema.
Why media.loc.collections is rated Low
Tool retrieves and queries public domain collection metadata without modifying or executing operations.
From the tool's definition Browse Library of Congress digital collections. Returns collection slugs needed for filtered search.
Attacks that exploit this kind of access
The rule that runs media.loc.collections 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.collections, this is the rule to start with:
media.loc.collections 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.collections call is checked against it from then on.
Questions about media.loc.collections
Browse Library of Congress digital collections — Civil War Photographs, Geography & Map Division, Rosa Parks Papers, etc. Returns collection slugs needed for filtered search. 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.collections accepts 1 parameter: limit. 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.collections: 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.collections 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.collections 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.collections. 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.collections 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