Low Risk

gitlab_list_wiki_pages

List wiki pages in a project.

How to control gitlab_list_wiki_pages ↓

What gitlab_list_wiki_pages does on Gitlab

AI agents call gitlab_list_wiki_pages 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.

Low Risk

Why gitlab_list_wiki_pages needs a policy

This tool retrieves and enumerates wiki pages, a non-destructive read operation with no side effects. The action is informational only, suitable for discovery or audit purposes. Misuse risk is minimal as it cannot alter, delete, or execute external operations.

From the tool's definition Tool name contains 'list' and description states 'List wiki pages in a project' — a read-only query operation that retrieves existing data without modification.

Documented attack patterns abuse exactly the kind of access gitlab_list_wiki_pages gives an agent:

How to control gitlab_list_wiki_pages

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_wiki_pages:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "gitlab_list_wiki_pages": {}
  }
}

gitlab_list_wiki_pages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Gitlab — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about gitlab_list_wiki_pages

What does the gitlab_list_wiki_pages tool do? +

List wiki pages in a project. It is categorised as a Read tool in the Gitlab MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gitlab_list_wiki_pages? +

Register the Gitlab MCP server in PolicyLayer and add a rule for gitlab_list_wiki_pages: 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.

What risk level is gitlab_list_wiki_pages? +

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

Can I rate-limit gitlab_list_wiki_pages? +

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

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

gitlab_list_wiki_pages 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.

Enforce policy on every Gitlab tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.