minimal_output
Return minimal repository information (default: true). When false, returns full GitHub API repository objects. (boolean, optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/minimal-output.md
What minimal_output does on GitHub
AI agents call minimal_output to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why minimal_output is rated Low
This is a parameter that controls the format and verbosity of data returned from repository queries. It retrieves information without creating, modifying, deleting, or executing any operations. The tool has no ability to alter state or trigger actions—it only affects how existing data is presented to the caller, making it a Read operation with minimal security risk.
From the tool's definition Tool description states it 'Return[s] minimal repository information' and controls output verbosity between minimal and 'full GitHub API repository objects'. This is a formatting/filtering parameter for data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs minimal_output 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 minimal_output, this is the rule to start with:
minimal_output is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every minimal_output call is checked against it from then on.
Questions about minimal_output
Return minimal repository information (default: true). When false, returns full GitHub API repository objects. (boolean, optional). It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP server in PolicyLayer and add a rule for minimal_output: 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.
minimal_output 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 minimal_output 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 minimal_output. 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.
minimal_output 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.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue