list_events

List events for the authenticated user (before/after: YYYY-MM-DD)

SERVERGitlab Mcp SOURCE@zereight/mcp-gitlab

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-zereight-gitlab-mcp/list-events.md

WHAT IT DOES

What list_events does on Gitlab Mcp

AI agents call list_events to retrieve information from Gitlab Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_events is rated Low

This tool only retrieves historical event records for the authenticated user. It has no side effects, does not modify data, execute code, delete data, or move money. The parameters (before/after dates) are used only for filtering the read operation. This is a straightforward read operation with minimal security risk.

From the tool's definition Tool name is 'list_events' and description states 'List events for the authenticated user', which retrieves/queries event data with optional date filtering. No modification, deletion, or execution capability indicated.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_events safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_events, this is the rule to start with:

list_events Allowed

list_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_events": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every list_events call is checked against it from then on.

FAQ

Questions about list_events

What does the list_events tool do? +

List events for the authenticated user (before/after: YYYY-MM-DD). It is categorised as a Read tool in the Gitlab Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_events? +

Register the Gitlab MCP server in PolicyLayer and add a rule for 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 Mcp. Nothing to install.

What risk level is list_events? +

list_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_events? +

Yes. Add a rate_limit block to the 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.

How do I block list_events completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides list_events? +

list_events is provided by the Gitlab MCP server (@zereight/mcp-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gitlab, and thousands of servers like it.

This server

All 215 Gitlab tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →