discover_tools

Discover and activate additional tool categories for this session. Call without arguments to see available categories.

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/discover-tools.md

WHAT IT DOES

What discover_tools does on Gitlab Mcp

AI agents call discover_tools 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 discover_tools is rated Low

This tool retrieves metadata about available tool categories within the GitLab MCP server session. It has no side effects, does not execute code or external operations, does not modify data, and does not involve financial transactions. It is purely informational/exploratory, fitting the Read category.

From the tool's definition Tool description states: 'Discover and activate additional tool categories for this session. Call without arguments to see available categories.' This is a query/discovery operation that lists available tools without modifying, executing, or deleting anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs discover_tools 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 discover_tools, this is the rule to start with:

discover_tools Allowed

discover_tools 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": {
    "discover_tools": {}
  }
}

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 discover_tools call is checked against it from then on.

FAQ

Questions about discover_tools

What does the discover_tools tool do? +

Discover and activate additional tool categories for this session. Call without arguments to see available categories. 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 discover_tools? +

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

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

Can I rate-limit discover_tools? +

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

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

discover_tools 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

The MCP Attack Database →

Guides

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