verbose

Show verbose output (optional, default: false) (boolean, optional)

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/verbose.md

WHAT IT DOES

What verbose does on GitHub

AI agents call verbose as a supporting operation in GitHub workflows.

RISK

Why verbose is rated Low

This entry does not describe an actionable tool but rather a boolean flag for controlling output verbosity. It has no side effects, does not retrieve data, and does not perform any operation on its own. It is likely metadata or a parameter definition incorrectly catalogued as a tool. Confidence is low due to the uninformative and atypical description.

From the tool's definition 'Show verbose output (optional, default: false) (boolean, optional)' - this appears to be a parameter/flag descriptor rather than an actual tool

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs verbose safely

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

verbose Rate-limited

verbose gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "verbose": {
      "limits": [
        {
          "counter": "verbose_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about verbose

What does the verbose tool do? +

Show verbose output (optional, default: false) (boolean, optional). It is categorised as a Other tool in the GitHub MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on verbose? +

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

What risk level is verbose? +

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

Can I rate-limit verbose? +

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

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

verbose is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →