cernopendata.datasets.browse
Browse and filter CERN Open Data collision and simulated datasets by experiment, publication year, collision energy, and keyword. Returns only records of type Dataset (66,000+ datasets). Useful for finding specific NanoAOD or MiniAOD simulation samples, real collision data, or derived datasets fo...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/cernopendata.datasets.browse.md
What cernopendata.datasets.browse does on Apibase
AI agents call cernopendata.datasets.browse 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 | — | Keyword filter within datasets (e.g. "NanoAOD", "MiniAOD", "Higgs") |
page | integer | — | Page number for pagination (default 1) |
year | string | — | Filter by publication year (e.g. "2015", "2016", "2012"). LHC Run 1: 2010–2013, Run 2: 2015–2016. |
limit | integer | — | Number of datasets to return (1–25, default 10) |
experiment | string | — | Filter by CERN experiment. CMS has 57K+ datasets, LHCb has 7K+, DELPHI has 12K+. |
collision_energy | string | — | Filter by collision energy (e.g. "13TeV", "8TeV", "7TeV"). Run 2 used 13 TeV, Run 1 used 7–8 TeV. |
Parameters from the server's own tool schema.
Why cernopendata.datasets.browse is rated Low
Tool only retrieves and filters publicly available dataset records with no side effects.
From the tool's definition Browse and filter CERN Open Data datasets
Attacks that exploit this kind of access
The rule that runs cernopendata.datasets.browse 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.datasets.browse, this is the rule to start with:
cernopendata.datasets.browse 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.datasets.browse call is checked against it from then on.
Questions about cernopendata.datasets.browse
Browse and filter CERN Open Data collision and simulated datasets by experiment, publication year, collision energy, and keyword. Returns only records of type Dataset (66,000+ datasets). Useful for finding specific NanoAOD or MiniAOD simulation samples, real collision data, or derived datasets for a given LHC run period. LHC Run 1 data: 2010–2012 at 7–8 TeV; Run 2 data: 2015–2016 at 13 TeV. Experiments: CMS (57K+), ALICE (171), ATLAS (184), LHCb (7K+), DELPHI (12K+). Supports pagination for large result sets. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
cernopendata.datasets.browse accepts 6 parameters: q, page, year, limit, experiment, collision_energy. 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.datasets.browse: 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.datasets.browse 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.datasets.browse 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.datasets.browse. 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.datasets.browse 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