restore
Runs dotnet restore to restore NuGet dependencies and returns structured results.
This record as markdown: /tools/io-github-dave-london-github/restore.md
What restore does on Github
AI agents invoke restore to trigger actions in Github. 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
The tool executes a dotnet CLI command on the host system to restore NuGet packages. This is an Execute category action because it triggers an external operation (running a process, potentially downloading packages from the internet, modifying the local package cache). It does not merely read data, and while restore is generally non-destructive, it does execute code and modifies the local environment.
From the tool's definition 'Runs dotnet restore to restore NuGet dependencies' — executes an external CLI command (dotnet restore)
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 Github, 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 Github, 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 Github MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Github 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 Github. 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 Github MCP server (@paretools/github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Github, and thousands of servers like it.
Across the catalogue