cernopendata.records.detail
Fetch full metadata for a specific CERN Open Data record by its ID. Returns complete details: title, type, experiment, publication date, abstract (HTML stripped), collections, availability, collision energy and type, accelerator, authors with ORCIDs, file listing (up to 5 files with sizes and EOS...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/cernopendata.records.detail.md
What cernopendata.records.detail does on Apibase
AI agents call cernopendata.records.detail 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 | Record ID from CERN Open Data portal (e.g. "5209", "50", "AOD"). Numeric for datasets/docs, string anchors for glossary terms. |
Parameters from the server's own tool schema.
Why cernopendata.records.detail is rated Low
Read-only retrieval of metadata from a public open data repository.
From the tool's definition Fetch full metadata for a specific CERN Open Data record
Attacks that exploit this kind of access
The rule that runs cernopendata.records.detail 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 cernopendata.records.detail, this is the rule to start with:
cernopendata.records.detail 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 cernopendata.records.detail call is checked against it from then on.
Questions about cernopendata.records.detail
Fetch full metadata for a specific CERN Open Data record by its ID. Returns complete details: title, type, experiment, publication date, abstract (HTML stripped), collections, availability, collision energy and type, accelerator, authors with ORCIDs, file listing (up to 5 files with sizes and EOS URIs), keywords, license, run period, and external links. Use cernopendata.records.search or cernopendata.datasets.browse to discover record IDs. IDs can be numeric (e.g. "5209") or string anchors for glossary terms (e.g. "AOD"). Most datasets are CC0 or CC-BY licensed. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
cernopendata.records.detail 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 cernopendata.records.detail: 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.
cernopendata.records.detail 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 cernopendata.records.detail 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 cernopendata.records.detail. 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.
cernopendata.records.detail 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