This record as markdown: /tools/io-github-dave-london-go/restore.md
What restore does on Go
AI agents invoke restore to trigger actions in Go. 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 restore is rated High
This tool executes an external shell command (dotnet restore) that fetches and installs NuGet packages from external sources. While it doesn't delete data or move money, it triggers an external operation (package resolution and download) whose effects depend on the project configuration. It falls under Execute as it runs a CLI tool with side effects (writing package files to disk, modifying lock files).
From the tool's definition 'Runs dotnet restore to restore NuGet dependencies' — actively executes a dotnet CLI command to fetch and install packages
Attacks that exploit this kind of access
The rule that runs restore safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Go, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For restore, this is the rule to start with:
restore 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 Go, apply this rule, and every restore call is checked against it from then on.
Questions about restore
Runs dotnet restore to restore NuGet dependencies and returns structured results. It is categorised as a Execute tool in the Go MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Go MCP server in PolicyLayer and add a rule for restore: 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 Go. Nothing to install.
restore 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 restore 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 restore. 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.
restore is provided by the Go 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 Go, and thousands of servers like it.
This server
Across the catalogue