Test connectivity to the CERN GitLab instance.
AI agents call test_connectivity 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.
This is a connectivity test—a non-intrusive probe that verifies reachability to a GitLab instance. It has no side effects, does not query or modify data, and does not execute code or commands. It is purely diagnostic in nature, making it a Read category tool with low severity and minimal blast radius if misused.
From the tool's definition Tool name 'test_connectivity' and description 'Test connectivity to the CERN GitLab instance' indicate a diagnostic operation that checks network/service availability without retrieving, modifying, or executing operations on data or systems.
Attacks that exploit this kind of access
Test connectivity to the CERN GitLab instance. 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 test_connectivity: 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.
test_connectivity 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 test_connectivity 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 test_connectivity. 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.
test_connectivity 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 →