cernopendata.glossary.lookup
Look up particle physics and high-energy physics (HEP) terms from the CERN Open Data glossary of 1,000+ terms. Returns matching entries with the term name, all known aliases/synonyms, a plain-text definition, category (generic, cms, etc.), related terms (see_also), and Wikipedia/external links. I...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/cernopendata.glossary.lookup.md
What cernopendata.glossary.lookup does on Apibase
AI agents call cernopendata.glossary.lookup 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 |
|---|---|---|---|
term | string | Yes | Physics term to look up in the HEP glossary (e.g. "quark", "hadron", "luminosity", "jet", "muon") |
limit | integer | — | Maximum number of matching terms to return (1–25, default 10) |
Parameters from the server's own tool schema.
Why cernopendata.glossary.lookup is rated Low
Purely retrieves glossary definitions with no side effects.
From the tool's definition Look up terms from the CERN Open Data glossary
Attacks that exploit this kind of access
The rule that runs cernopendata.glossary.lookup 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.glossary.lookup, this is the rule to start with:
cernopendata.glossary.lookup 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.glossary.lookup call is checked against it from then on.
Questions about cernopendata.glossary.lookup
Look up particle physics and high-energy physics (HEP) terms from the CERN Open Data glossary of 1,000+ terms. Returns matching entries with the term name, all known aliases/synonyms, a plain-text definition, category (generic, cms, etc.), related terms (see_also), and Wikipedia/external links. Ideal for AI agents that need to explain or understand HEP concepts like "quark", "hadron", "luminosity", "trigger", "AOD", "CMSSW", "jet", "b-tagging", or any other particle physics terminology. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
cernopendata.glossary.lookup accepts 2 parameters: term, limit. Required: term. 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.glossary.lookup: 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.glossary.lookup 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.glossary.lookup 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.glossary.lookup. 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.glossary.lookup 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