mod-tidy

Runs go mod tidy to add missing and remove unused module dependencies.

SERVERGit SOURCEDave-London/Pare

High RISK CLASS

Category Execute

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-dave-london-git/mod-tidy.md

WHAT IT DOES

What mod-tidy does on Git

AI agents invoke mod-tidy to trigger actions in Git. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why mod-tidy is rated High

This tool executes a shell command (go mod tidy) that modifies the go.mod and go.sum files by adding missing dependencies and removing unused ones. It has real side effects on the project's dependency files, making it an Execute-level operation. Severity is medium because while it changes project files, the effects are typically reversible via version control.

From the tool's definition Runs go mod tidy to add missing and remove unused module dependencies

Attacks that exploit this kind of access

RECOMMENDED RULE

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

mod-tidy Rate-limited

mod-tidy stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mod-tidy": {
      "limits": [
        {
          "counter": "mod-tidy_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about mod-tidy

What does the mod-tidy tool do? +

Runs go mod tidy to add missing and remove unused module dependencies. It is categorised as a Execute tool in the Git MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on mod-tidy? +

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

mod-tidy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit mod-tidy? +

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

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

mod-tidy 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →