mod-tidy
Runs go mod tidy to add missing and remove unused module dependencies.
This record as markdown: /tools/io-github-dave-london-pare-search/mod-tidy.md
What mod-tidy does on Search
AI agents invoke mod-tidy to trigger actions in Search. 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.
Why mod-tidy is rated High
This tool executes an external command (go mod tidy) which runs code and modifies project dependency files. It triggers an external operation (Go module management) and rewrites go.mod/go.sum, making it Execute rather than Write since it runs a subprocess with side effects beyond simple data mutation.
From the tool's definition 'Runs go mod tidy' — executes a Go toolchain command that modifies go.mod and go.sum files
Attacks that exploit this kind of access
The rule that runs mod-tidy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Search, 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 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Search, apply this rule, and every mod-tidy call is checked against it from then on.
Questions about mod-tidy
Runs go mod tidy to add missing and remove unused module dependencies. It is categorised as a Execute tool in the Search MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Search 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 Search. Nothing to install.
mod-tidy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
mod-tidy is provided by the Search MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Search, and thousands of servers like it.
Across the catalogue