flake-show

Shows the outputs of a Nix flake as a structured tree. Uses --json for machine-parseable output by default.

SERVERGit SOURCEDave-London/Pare

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-dave-london-git/flake-show.md

WHAT IT DOES

What flake-show does on Git

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

RISK

Why flake-show is rated Low

This tool retrieves and presents information about Nix flake outputs in a structured, machine-parseable format. There are no side effects, state changes, or triggering of external operations. It is a read-only query operation that falls squarely in the Read category with low severity, as misuse would only expose information rather than cause damage.

From the tool's definition Tool 'flake-show' displays outputs of a Nix flake as structured tree using --json. The verb 'show' and description language ('shows', 'structured tree') indicate pure data retrieval with no modification, creation, or execution of external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs flake-show safely

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

flake-show Allowed

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

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

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

FAQ

Questions about flake-show

What does the flake-show tool do? +

Shows the outputs of a Nix flake as a structured tree. Uses --json for machine-parseable output by default. It is categorised as a Read tool in the Git MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on flake-show? +

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

What risk level is flake-show? +

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

Can I rate-limit flake-show? +

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

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

flake-show is provided by the Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Git, and thousands of servers like it.

This server

All 202 Git tools →

Across the catalogue

The MCP Attack Database →

Guides

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