Search for code snippets within a specific LHCb software stack (e.g.,
AI agents call search_lhcb_stack to retrieve information from CERN GitLab MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs code discovery and search operations across the LHCb software stack, which is a read-only action that retrieves existing information without side effects. No data is created, modified, deleted, or executed. This aligns with the 'Read' category definition of retrieving or querying data with no side effects.
From the tool's definition Tool name 'search_lhcb_stack' and description indicates searching for code snippets within a specific software stack. This is a read-only retrieval operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search for code snippets within a specific LHCb software stack (e.g.,. It is categorised as a Read tool in the CERN GitLab MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CERN GitLab MCP Server MCP server in PolicyLayer and add a rule for search_lhcb_stack: 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 CERN GitLab MCP Server. Nothing to install.
search_lhcb_stack 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 search_lhcb_stack 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 search_lhcb_stack. 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.
search_lhcb_stack is provided by the CERN GitLab MCP Server MCP server (mohamedelashri/cerngitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →