restore

Runs dotnet restore to restore NuGet dependencies and returns structured results.

SERVERBuild 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-build/restore.md

WHAT IT DOES

What restore does on Build

AI agents invoke restore to trigger actions in Build. 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 restore is rated High

dotnet restore is an external command execution that downloads packages from the internet and writes files to disk. While not purely destructive, it runs an external process with side effects (network access, file writes), placing it firmly in Execute. Misuse could introduce malicious packages or alter dependency state.

From the tool's definition 'Runs dotnet restore' — executes an external dotnet CLI command that performs network operations (downloading NuGet packages) and modifies the local file system (restoring dependencies).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs restore safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Build, 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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "restore": {
      "limits": [
        {
          "counter": "restore_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 Build, apply this rule, and every restore call is checked against it from then on.

FAQ

Questions about restore

What does the restore tool do? +

Runs dotnet restore to restore NuGet dependencies and returns structured results. It is categorised as a Execute tool in the Build MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on restore? +

Register the Build 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 Build. Nothing to install.

What risk level is restore? +

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

Can I rate-limit restore? +

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.

How do I block restore completely? +

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.

What MCP server provides restore? +

restore is provided by the Build 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 Build, and thousands of servers like it.

This server

All 202 Build 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 →