dpla.archives.facets
Get top facet counts (subjects, providers/institutions, media types, US states) across the entire DPLA collection or scoped to a search query. Useful for discovering what subject areas, contributing libraries, or media types dominate a given topic. Returns ranked term lists with counts for four d...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/dpla.archives.facets.md
What dpla.archives.facets does on Apibase
AI agents call dpla.archives.facets 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 |
|---|---|---|---|
q | string | — | Optional query to scope the facets (e.g. "civil war" returns top subjects/providers/types within that query). Omit for global top facets. |
facet_size | integer | — | Number of top terms to return per facet dimension, 1–50 (default: 10) |
Parameters from the server's own tool schema.
Why dpla.archives.facets is rated Low
Retrieves aggregated metadata counts from DPLA archives; no data modification or side effects.
From the tool's definition Get top facet counts, scoped to search query, returns ranked term lists
Attacks that exploit this kind of access
The rule that runs dpla.archives.facets 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.facets, this is the rule to start with:
dpla.archives.facets 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.facets call is checked against it from then on.
Questions about dpla.archives.facets
Get top facet counts (subjects, providers/institutions, media types, US states) across the entire DPLA collection or scoped to a search query. Useful for discovering what subject areas, contributing libraries, or media types dominate a given topic. Returns ranked term lists with counts for four dimensions: subject, provider, type, and state. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
dpla.archives.facets accepts 2 parameters: q, facet_size. 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.facets: 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.facets 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.facets 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.facets. 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.facets 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