cern-search-by-experiment
Search CERN Open Data records scoped to a specific experiment (CMS, ATLAS, LHCb, ALICE).
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/cern-search-by-experiment.md
What cern-search-by-experiment does on Meta Data Mcp
AI agents call cern-search-by-experiment to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why cern-search-by-experiment is rated Low
This tool retrieves data from CERN's public open data repository by querying records filtered by experiment type. It has no side effects, cannot modify data, and poses minimal risk if misused by an AI agent—worst case being information retrieval from already-public sources. This is a straightforward Read operation.
From the tool's definition Tool name contains 'search' and description states 'Search CERN Open Data records'. The action is querying/retrieving publicly available open data with no modification, creation, deletion, or execution of code.
Attacks that exploit this kind of access
The rule that runs cern-search-by-experiment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cern-search-by-experiment, this is the rule to start with:
cern-search-by-experiment 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 Meta Data Mcp, apply this rule, and every cern-search-by-experiment call is checked against it from then on.
Questions about cern-search-by-experiment
Search CERN Open Data records scoped to a specific experiment (CMS, ATLAS, LHCb, ALICE). It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.
Register the Meta Data MCP server in PolicyLayer and add a rule for cern-search-by-experiment: 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 Meta Data Mcp. Nothing to install.
cern-search-by-experiment 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 cern-search-by-experiment 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 cern-search-by-experiment. 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.
cern-search-by-experiment is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Data, and thousands of servers like it.
This server
Across the catalogue