List current user events.
AI agents call gitlab_list_events to retrieve information from Gitlab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical event information for the current user (such as activity logs, merge requests, issues, etc.). It has no side effects—it only queries and returns existing data. This is a straightforward read operation with minimal risk exposure.
From the tool's definition The tool name and description indicate a query operation: 'List current user events' retrieves and returns event data without modifying any resources.
Documented attack patterns abuse exactly the kind of access gitlab_list_events gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gitlab, and nothing reaches the server without passing your rules. This is the rule we recommend for gitlab_list_events:
{
"version": "1",
"default": "deny",
"tools": {
"gitlab_list_events": {}
}
}gitlab_list_events is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List current user events. It is categorised as a Read tool in the Gitlab MCP Server, which means it retrieves data without modifying state.
Register the Gitlab MCP server in PolicyLayer and add a rule for gitlab_list_events: 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 Gitlab. Nothing to install.
gitlab_list_events 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 gitlab_list_events 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 gitlab_list_events. 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.
gitlab_list_events is provided by the Gitlab MCP server (mcpland/gitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gitlab, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
190 Gitlab tools catalogued and risk-classified — across an index of 43,000+ MCP servers.