cernopendata.records.search
Search 80,000+ particle physics records from the CERN Open Data portal, covering CMS, ATLAS, ALICE, LHCb, and legacy experiments. Filter by record type (Dataset, Documentation, Software, Supplementaries), experiment, and keyword. Each record includes title, type, experiment, publication date, ava...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/cernopendata.records.search.md
What cernopendata.records.search does on Apibase
AI agents call cernopendata.records.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 |
|---|---|---|---|
q | string | — | Full-text search query (e.g. "higgs boson", "dark matter", "Z boson decay") |
page | integer | — | Page number for pagination (default 1) |
type | string | — | Filter by record type: Dataset (collision/simulated data), Documentation, Software, Supplementaries, Environment, Glossary, News |
limit | integer | — | Number of results to return (1–25, default 10) |
experiment | string | — | Filter by CERN experiment (e.g. CMS, ATLAS, ALICE, LHCb). CMS has the most open data. |
Parameters from the server's own tool schema.
Why cernopendata.records.search is rated Low
Tool queries public scientific data with no side effects or modification capabilities.
From the tool's definition Search 80,000+ particle physics records from CERN Open Data portal. Filter by type, experiment, keyword.
Attacks that exploit this kind of access
The rule that runs cernopendata.records.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 cernopendata.records.search, this is the rule to start with:
cernopendata.records.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 cernopendata.records.search call is checked against it from then on.
Questions about cernopendata.records.search
Search 80,000+ particle physics records from the CERN Open Data portal, covering CMS, ATLAS, ALICE, LHCb, and legacy experiments. Filter by record type (Dataset, Documentation, Software, Supplementaries), experiment, and keyword. Each record includes title, type, experiment, publication date, availability, collision energy, abstract snippet, and collections. Supports pagination. Free, no auth required. Records include collision and simulated datasets in NanoAOD/MiniAOD/AOD format, plus educational resources, software, and documentation from the Large Hadron Collider era. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
cernopendata.records.search accepts 5 parameters: q, page, type, limit, experiment. 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.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.
cernopendata.records.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 cernopendata.records.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 cernopendata.records.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.
cernopendata.records.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