culture.europeana.record
Full metadata for a single cultural heritage object — title, creator, description, date, language, source, rights, high-res image URL, provider institution, landing page. Use ID from search results (Europeana)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/culture.europeana.record.md
What culture.europeana.record does on Apibase
AI agents call culture.europeana.record 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 |
|---|---|---|---|
id | string | Yes | Europeana record ID from search results (e.g. "/09102/_GNM_693983" or "09102/_GNM_693983") |
Parameters from the server's own tool schema.
Why culture.europeana.record is rated Low
Queries and retrieves public cultural heritage metadata with no write, execute, or destructive capabilities.
From the tool's definition Full metadata for a single cultural heritage object — retrieves title, creator, description, date, language, source, rights, image URL
Attacks that exploit this kind of access
The rule that runs culture.europeana.record 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 culture.europeana.record, this is the rule to start with:
culture.europeana.record 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 culture.europeana.record call is checked against it from then on.
Questions about culture.europeana.record
Full metadata for a single cultural heritage object — title, creator, description, date, language, source, rights, high-res image URL, provider institution, landing page. Use ID from search results (Europeana). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
culture.europeana.record accepts 1 parameter: id. Required: 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 culture.europeana.record: 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.
culture.europeana.record 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 culture.europeana.record 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 culture.europeana.record. 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.
culture.europeana.record 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